Kubernetes
OOM Threshold & Memory Limit Calculator
Enter P99 observed memory and workload type to compute recommended memory request, limit, OOM kill threshold, and safe alerting threshold.
No data is transmitted — everything runs locallyTool
About this tool
OOM Threshold & Memory Limit Calculator
The OOM Threshold Calculator computes safe memory request and limit from P99 usage with workload-type overhead, showing OOM kill threshold and alerting recommendations.
• Set memory limits that won't OOM kill during normal traffic spikes
• Calculate JVM heap size that fits within container memory limit
• Determine alerting threshold for memory usage before OOM kill risk
• Understand QoS class implications of request vs limit configuration
Affiliate disclosure
Uptime, incident, and on-call management. Better Stack provides status pages, incident management, and on-call scheduling for engineering teams.
View OOM events with Better Stack
External site · Independent provider · We may receive a commission · Not a recommendation
FAQ
What does this tool tell you?
The OOM Threshold Calculator computes safe memory request and limit from P99 usage with workload-type overhead, showing OOM kill threshold and alerting recommendations.
What affects the result most?
OOM kill threshold: container is killed when memory usage exceeds memory limit. Working set vs RSS: Kubernetes uses working set (RSS + file cache) for eviction decisions. Eviction thresholds: kubelet evicts pods when node memory available < eviction threshold (default 100Mi).
How should I use the result?
The calculation is deterministic — the same inputs always produce the same output — so the most useful workflow is to vary one input at a time and see which factor moves the result most. That tells you where to focus your attention before committing to a decision.
Related tools