I'm happy to help you understand how to set the resources for egress in LiveKit! You can easily configure the CPU and memory requirements in the Helm chart configuration under the

resources

field. This setup lets you specify CPU and memory limits and requests for the egress service containers, ensuring everything runs smoothly. For instance, in the

egress-sample.yaml

file, you have the option to define the

requests

and

limits

for CPU and memory. This helps make sure the egress service has just the right amount of resources it needs. Plus, you can tweak the CPU cost for different types of egress operations to better manage how resources are allocated: • Room Composite: Default CPU cost is 3.0 • Web: Default CPU cost is 3.0 • Track Composite: Default CPU cost is 2.0 • Track: Default CPU cost is 1.0 Feel free to customize these values based on what works best for your application’s needs — this way, you can optimize both performance and resource usage effectively. Sources: egress/templates/deployment.yaml | README.md