For about the past week or so I've noticed that mythfilldatabase is taking many hours to run. Up about a week ago mythfilldatabase was running daily and taking no longer than 30 minutes or so (not sure exact times, but definitely not near as long as it's taking now). Now, mythfilldatabase downloads new listings and everything appears fine. Then, when it gets to 'Marking episode first showings' it takes FOREVER. Running it with '-v all' shows these type of updates running about 1 per second:<br>
<br>2008-12-12 12:26:10.008 MSqlQuery: UPDATE program set first = 1 WHERE starttime = '2008-12-11T11:00:00' AND programid = 'EP005984670029';<br>2008-12-12 12:26:11.168 MSqlQuery: UPDATE program set first = 1 WHERE starttime = '2008-12-11T10:00:00' AND programid = 'EP005984670030';<br>
2008-12-12 12:26:12.314 MSqlQuery: UPDATE program set first = 1 WHERE starttime = '2008-12-11T15:00:00' AND programid = 'EP005984670031';<br>2008-12-12 12:26:13.476 MSqlQuery: UPDATE program set first = 1 WHERE starttime = '2008-12-13T13:00:00' AND programid = 'EP005987610238';<br>
<br>And mysqld is using 95-100% CPU for this entire time. My first thought was that I needed to repair/optimize the program table so I ran optimize_mythdb.pl, but that didn't seem to make any difference at all. <br>
<br>I'm currently running 0.20.2-fixes and I don't believe I've made any changes to this machine in ages. This is a master backend running headless so there should be no frontend activity on this machine at all. <br>
<br>I'm currently in the process of setting up a new backend with 0.21 and once that is set up I will be migrating all my frontends to use that so this is only a short-term problem. However, I'm at least several weeks away from having that new backend completed and in the meantime this CPU hogging/DB slowness is really killing the WAF. Anyone have any ideas on what might be the issue or at least where to start looking?<br>
<br>Thanks,<br>Brad<br><br>