You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the GUI you can set a value for "Parallel Jobs".
When videos get encoded however, ffmpeg is ran with --threads 8 (probably with as many parallel instances as the Parallel Jobs setting value is).
Now I don't know the internals of this tool but I would suggest ffmpeg being run with a super conservative -threads 1 so it does not surprisingly use more cores than what the user set Parallel Jobs to.
The text was updated successfully, but these errors were encountered:
We measured performance to be better with --threads 8, and there didn't seem to be much downside even when there are more total threads than cores. Many jobs are I/O bound and not CPU bound, so many jobs use less than 1 core at any given time.
You mention a user being surprised if more cores are used instantaneously than the number of "Parallel Jobs". What's the practical problem? Is it something we could explain to the user with documentation or a short snippet next to the Parallel Jobs setting?
In the GUI you can set a value for "Parallel Jobs".
When videos get encoded however, ffmpeg is ran with
--threads 8
(probably with as many parallel instances as the Parallel Jobs setting value is).Now I don't know the internals of this tool but I would suggest ffmpeg being run with a super conservative
-threads 1
so it does not surprisingly use more cores than what the user set Parallel Jobs to.The text was updated successfully, but these errors were encountered: