Two encode jobs get started at the same time

[automatic-ripping-machine]

Two encode jobs get started at the same time

[ahnooie]

This is intended behavior. The ARM scripts calls the transcoding command with "batch" which waits until the system load is below 1.5 and then queues the next transcoding job. The only way you got two transcoding jobs running simultaneously is that your system load fell below 1.5 which generally means you had CPU cycles to spare (unless you're running a 1 core CPU). This is not going to be perfect for every system but overall I think it's a good compromise between running everything in serial and not maximizing the cpu and running it all in parallel and it takes forever to finish transcoding.

The only way I can think of to make this better is to use the atd command instead of batch where you can specify the desired load before the command executes instead of the default of 1.5.

[TheFiZi]

Thanks for the explanation. I'm using a 4 CPU VM to do my transcoding so there must have been spare CPU cycles lying around.

What's interesting is when one of the two jobs finish another does not immediately start. The box waits until both jobs are done and then fires up two more jobs.

[ahnooie]

Hmmm. I bet both jobs are in the queue waiting and finally when the CPU drops below 1.5 both jobs launch at the same time.

[TheFiZi]

That's my guess as well based on your explanation of how the batch process works.