[mythtv-users] slow mythcommflag and setting JobQueueCPU in 'settings' mysql table
Michael T. Dean
mtdean at thirdcontact.com
Wed Dec 16 01:03:24 UTC 2009
On 12/15/2009 01:31 AM, Bill Bogstad wrote:
> I recently decided to redo commercial flagging on all my recordings.
> I made the mistake of using 'mythcommflag --all --queue' to do so.
> Unfortunately, that throttles mythcommflag so much that my backend is
> running at only 10% CPU utilization and it looked like it was going to
> take a week to finish. After some review of the source, it seems that
> in addition to using nice() to reduce it's load; mythcommflag also
> sleeps after every frame (or something like that).
The select-box setting:
This setting controls approximately how much CPU jobs in the queue may
consume. On 'High', all available CPU time may be used which could cause
problems on slower systems.
Where High = go all out, Medium = nice 17, Low = nice 17 + sleep.
> Apparently the
> sleep can be turned off if the JobQueueCPU value in the settings
> table of the mysql database is set to something larger then 0. The
> problem is I can't seem to find anyway to set this value other then to
> hack the database. (I've done this (set it to 1) and it is now maxing
> out one of the cores on my CPU.)
> However, for future reference, is there a more straightforward way to
> change the setting of JobQueueCPU?
The setting quoted above is in mythtv-setup under General, several (5?)
screens in on the screen, "Job Queue (Backend-Specific)."
> I'm on 0.21 so maybe a new interface has been created in 0.22.
Same place in both.
More information about the mythtv-users