[mythtv-commits] Re: Ticket #551: Scheduler consuming all CPU cycles and disk bandwidth (via mysql).

[MythTV]

#551: Scheduler consuming all CPU cycles and disk bandwidth (via mysql).
-----------------------+----------------------------------------------------
 Reporter:  anonymous  |        Owner:  gigem
     Type:  defect     |       Status:  new  
 Priority:  critical   |    Milestone:  0.19 
Component:  mythtv     |      Version:  head 
 Severity:  medium     |   Resolution:       
-----------------------+----------------------------------------------------
Comment (by danielk):

 BJM, my reschedules are not so bad as to destroy my recordings. Perhaps
 because the DB uses a seperate disk. But I've attached two examples that
 do spend an extremely long time in a single query nonetheless. One is just
 a basic run on a DB with cruft from EIT scans, the other is with a
 pristene 'program' table after clearing it out completely and getting all
 new data via datadirect.

 As you can see it takes between 30x and 60x times the time it really
 should in either case, but AddNewRecords is twice as slow on a non-
 pristene db. There were approximately the same number of rows 34000 vs
 36000 in the program table.

 I also tried wacky values for the title, subtitle, and programid columns.
 The duplicates in the title sped up the query quite a bit, while
 duplicates in the others increased the query time, but only by a few
 milliseconds.

-- 
Ticket URL: <http://svn.mythtv.org/trac/ticket/551>
MythTV <http://www.mythtv.org/>
MythTV