[mythtv-users] 0.25 lookup metadata as part of jobqueue?

[Michael T. Dean]

On 03/11/2012 02:26 PM, Steven Adeff wrote:
> On Sun, Mar 11, 2012 at 2:12 PM, Raymond Wagner wrote:
>> On 3/11/2012 13:47, Scott&  Nicole Harris wrote:
>>>>> On Sun, Mar 11, 2012 at 11:43 AM, Raymond Wagner wrote:
>>>>>> On 3/11/2012 08:03, Scott&     Nicole Harris wrote:
>>>>>>> It would also be nice to set a different max jobs per job type.  i.e.
>>>>>>> Allow
>>>>>>> 4 commercial flag jobs but only 1 transcode job at a time.
>>>>>> That's still far from optimal.  Commercial detection can run in realtime
>>>>>> behind a recording, or at full speed behind a recording.  At full speed,
>>>>>> it will fairly efficiency balance over two cores, meaning those four
>>>>>> jobs would saturate a dual socket, quad core server.  In realtime, all
>>>>>> of those commercial detection runs will sit idle for the first ten
>>>>>> minutes, waiting for enough data to do icon detection, and then catch up
>>>>>> as fast as they can to the in-progress recording, again saturating that
>>>>>> high end server.  Depending on how many simultaneous recordings you
>>>>>> have, you may not have a choice of which mode the jobs are going to run
>>>>>> in.
>>>>> So if I have a dual core processor, I run my commercial detection jobs
>>>>> "real time", and I have say, 7 tuners, would it make sense to allow
>>>>> more than two commercial detection jobs to run at a time so that all
>>>>> current recordings are being processed or is it better to only allow
>>>>> one job per core?
>>>> If you have a dual core processor, are allowing two simultaneous
>>>> commercial detection jobs, and are recording seven shows, the first two
>>>> jobs that get added to the database will run in real time, assuming your
>>>> CPU has enough performance to achieve that.  The remaining five will
>>>> queue up and run full speed once the first two recordings are finished,
>>>> two at a time, and every so slightly less than half their maximum speed,
>>>> due to the two potentially competing over shared resources.
>>> Meaning, if I understand you correctly, that you'd actually have all your
>>> jobs faster by allowing only one job, correct?
>> For the specific case of non-realtime commercial detection on a single
>> or dual core CPU, yes.  One or two jobs would be roughly the same.  More
>> than two and you're going to start hitting some noticeable resource
>> contention.
> right now I have mine set to low

That is your real problem.

>   + 2 jobs on my 2 core processor.

You'd get your jobs finished faster with medium CPU and one job (on the 
host) than low CPU and 2 jobs on the host.

See the post I linked, before:

http://www.gossamer-threads.com/lists/mythtv/users/499517#499517

Mike