Author can be reached through [email protected]
Test environment
These are the specs for the VM hosting mediasoup workers and the control plane:
- 4c/4t Intel(R) Xeon(R) Platinum 8168 CPU @ 2.70GHz
- 8 GB RAM
- The VM had a baseline memory usage of, roughly, 2.8 GB. Since initial memory usage of mediasoup workers is negligible at best, I've decided not to normalize the memory data to
0
in the graphs.
- Ubuntu Bionic, standard kernel
- Control plane is running under Node.js 12 and workers are running directly in the host (no containers)
- System metrics were collected with
dstat
with a 1 second collection interval
Overall test characteristics:
- 4 mediasoup workers with roughly even distribution of producer/consumer load
- Test plans were centered around scenarios with 1450 VP8 streams spanning across 25 producers and 1425 consumers. Streams were added at roughly even intervals
- Each media stream had its own transport and simulcast wasn't used
- An YAML representation of worker|transports|router settings used can be found here: https://gist.github.com/prlanzarin/6a10cd1c339eb2abad5ef89a54dd2d7a