Currently conversions only handle a single sequential queue. The premise is that each conversion takes up the appropriate amount of system resources to get its job done, but the reality is that a lot of resources are left on the table.
It would be great to have an option to set the amount of conversions to run in parallel
1 Like
This would be amazing!
Iāve requested the same thing in the past as well:
It would be great if the Transcoder Settings had configuration to allow for the āOptimizeā queue to support more than one processing job at a time.
Currently I run Plex in a distributed manner in which actual transcoding jobs get offloaded to other servers in my network, so technically I could be optimizing multiple items in parallel and just have PMS monitor the progress without actually doing any of the work.
However, the Conversion queue is fixed to just one job at a time leaving the serverā¦
Combining this functionality of converting multiple items in parallel with the clusterplex dockermod (GitHub - pabloromeo/clusterplex: ClusterPlex is an extended version of Plex, which supports distributed Workers across a cluster to handle transcoding requests. ) you could convert in parallel across a swarm of transcoding nodes without overloading PMS itself.
system
Closed
December 27, 2021, 2:31pm
3
This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.