Hi everyone, We recently migrated from LiveKit Cloud to self-hosted LiveKit on Azure. Setup: • D8as_v5 VM (8 vCPU, 32 GB RAM) • LiveKit + SIP + Redis + Egress + CoTURN • Room composite Egress recording to Azure Blob • Docker Compose • 3–5 Egress replicas Calls/audio work perfectly, but during concurrent load some recordings fail with: • "can not accept request" • "Start signal not received" • "no response from servers" After scaling Egress replicas and increasing shm_size, stability improved. Question: • Is ~35–40% CPU usage per active room composite recording normal? • Roughly how many concurrent recordings should this VM handle safely? • Is dedicated Egress infrastructure recommended for production? On LiveKit Cloud, much higher concurrency worked for us at lower cost, so trying to understand best practices for self-hosted scaling. Thanks!

Yes, composite recording is cpu intensive, and you should have dedicated egress cluster

can u please tell me more about it?

what do you want to know

like we should run dedicated egress servers? because currently i am running everything on single server ps: ss

Yes, you should have dedicated capacity for egress, its cpu bound, and will interfere with other components

ok thanks for the guidance

I am curious why you would pick self hosted over cloud?

For security point of view and data retention