livepeer_bench
tool and the
common output rendition configuration
transcodingOptions.json
you stored during the benchmarking, you can work with
this guide to fine tune your configuration:
OrchestratorCapped
, to the
gateway and transcoders and they will stop receiving work from
orchestrators. The session limit should then be set depending on available
hardware and bandwidth.
-maxSessions
parameter to the node where
they should be set based on taking the minimum of:
X
was less than or equal 0.8. This leaves a ~20% buffer for
upload/download within real-time.
livepeer_bench
tool to benchmark
transcoding for a range of concurrent sessions:{1..20}
) to reflect the maximum number of concurrent
sessions you want to benchmark. If at 20 maximum concurrent sessions real-time
duration is still below 1.0, you should increase the maximum number of
concurrent sessions.
bench.log
.
1080p30fps
):
upstream/downstream
speed of 100 Mbps
should reliably be able to serve/process ~16 streams.
However, as not all streams’ segments may be processed at the same time, you may
be able to extend this by an additional ~20%.
-maxSessions
flag.
Session management in orchestrators and transcoders is still constantly being
improved. Your mileage may vary with this approach; you may find that your
orchestrator or transcoder performance may be affected with a higher session
limit.
Further adjusting the session limit values after performing work on the network
may be necessary.
-maxSessions
flag is used to set session limits on both orchestrators and
transcoders.
For Example:
For a combined orchestrator and transcoder, set the session limit to 30: