Understanding Shared CPU, RAM, and Storage Quotas // NodeFlux Docs

Learn how hardware resource limits are enforced across shared node infrastructure and how to optimize your workloads within allocations. ## Steps 1. Review your service resource allocations (RAM, vCore percentage, NVMe storage) in the manager panel detail view. 2. Understand that CPU allocations are managed via Linux cgroups; services burst up to their vCore limit without starving neighboring workloads. 3. Monitor RAM utilization via container logs; reaching 100% memory allocation triggers the Linux Out-Of-Memory (OOM) killer, resulting in automated container restart. 4. Keep NVMe disk usage below 90% quota by periodically clearing temporary files, old log files, and world backup archives. 5. If your workload consistently hits resource caps, optimize application memory configuration or submit a plan adjustment request via support ticket. ## Notes - NodeFlux free plans provide dedicated container isolation while sharing underlying physical host resources fairly. - OOM crashes can be identified in service logs when a service suddenly stops without standard exit codes. ## Warning Continuous heavy CPU or RAM overuse that impacts host stability may cause automated rate-limiting or service temporary suspension.