We are using livekit Scale plan and now on boarding Enterprise as well. Jesse and Jason is working with us. But, we could find this issues. The major issue is; When we run the system with around 15 concurrent calls, it scales up to 4 replicas based on both 50% CPU and 50% memory utilization. My concern here is that as concurrency increases, more replicas will be required. If LiveKit (or our service) takes time to spin up new containers, this could negatively impact user experience during traffic spikes. I’d love to hear your thoughts on: • How the race condition could affect calls where participants are still active • Whether there are any obvious CPU-heavy paths in the current implementation • What strategies you’d recommend to mitigate scaling and startup latency issues under higher concurrency Looking forward to your guidance. my start up script: Run the LiveKit agent

```
```cli.run_app(

    WorkerOptions(

        *entrypoint_fnc***=**entrypoint,

        *prewarm_fnc***=**prewarm,

        *worker_type***=**WorkerType.ROOM,

        *initialize_process_timeout***=**120.0,

        *agent_name***=**settings.agent_name,

    )

Lets stop using this thread. It is getting confusing. Let use this thread instead https://community.livekit.io/t/livekit-worker-memory-is-exceeding-100-with-7-concurrent-session-and-8gb-memory-4-vcpu/286/11