--- title: Java JVM CPU and Memory Requests and Limits in Kubernetes description: A deep technical breakdown explains why sizing a JVM inside a Kubernetes container requires coordinating four coupled decisions: container memory limit, heap... canonical: https://daily.dev/posts/java-jvm-cpu-and-memory-requests-and-limits-in-kubernetes-9pj5al4jr twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Java JVM CPU and Memory Requests and Limits in Kubernetes | daily.dev og:description: A deep technical breakdown explains why sizing a JVM inside a Kubernetes container requires coordinating four coupled decisions: container memory limit, heap... og:url: https://daily.dev/posts/java-jvm-cpu-and-memory-requests-and-limits-in-kubernetes-9pj5al4jr og:image: https://api.daily.dev/og/posts/9Pj5AL4jR.png og:image:alt: Java JVM CPU and Memory Requests and Limits in Kubernetes og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Java JVM CPU and Memory Requests and Limits in Kubernetes **[LearnKube](https://daily.dev/sources/learnkube)** · 21 min read · 3 upvotes · 0 comments ## Summary A deep technical breakdown explains why sizing a JVM inside a Kubernetes container requires coordinating four coupled decisions: container memory limit, heap size, garbage collector selection, and CPU quota. It distinguishes JVM heap OOM (OutOfMemoryError) from container OOM (OOMKilled), covers cgroup v2 memory accounting, thread stack memory, virtual threads vs platform threads, and how CPU limits translate into HotSpot's processor count and GC worker pool sizing. Includes Docker demos showing how -Xmx, MaxRAMPercentage, and -Xss settings interact with container limits, plus guidance on collecting JVM and container metrics together (via Micrometer/Actuator or Prometheus JMX Exporter) to properly size these settings under real workloads. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### Why does my Java pod get OOMKilled by Kubernetes even though the JVM never threw an OutOfMemoryError? A JVM in a container has two separate memory boundaries: the Java heap, capped by -Xmx or MaxRAMPercentage, and the container's total memory, capped by limits.memory. The container limit covers the heap plus metaspace, code cache, thread stacks, direct buffers, GC structures, and native libraries. If total memory hits that limit first, the kernel kills the process before HotSpot can report a heap OutOfMemoryError, and Kubernetes reports the reason as OOMKilled. _Track how memory boundaries interact when debugging container crashes on daily.dev._ ### How much container memory should I leave outside the JVM heap when setting -XX:MaxRAMPercentage in Kubernetes? Leave enough room for thread stacks, metaspace, code cache, direct buffers, and GC structures beyond whatever percentage of the container limit the heap uses. In one 512MiB example, setting MaxRAMPercentage=50.0 gave a roughly 247MiB heap, leaving about 256MiB for everything else; in a 256MiB container, a 50% target left about 133MiB outside the heap, which was enough to avoid an OOMKilled process, while a heap sized to the full limit was not. _Developers tuning JVM heap percentages against container limits can compare notes on daily.dev._ ### Does a Kubernetes CPU limit affect Java garbage collection pause times? Yes, a lower CPU limit can make garbage collection pauses noticeably longer. In one comparison, cutting the CPU limit to half a CPU caused the container to hit its quota during collection cycles, so the cgroup throttled and the collector had to wait for the next quota period; reported GC collection time rose from 82ms to 331ms and average System.gc() latency rose from 2ms to 18ms in that test. _Anyone sizing CPU limits for latency-sensitive JVM workloads can dig into these trade-offs on daily.dev._ ## Similar posts on daily.dev - [Kubernetes Requests and Limits: How to Right-Size Pods Without Breaking Reliability](https://daily.dev/posts/kubernetes-requests-and-limits-how-to-right-size-pods-without-breaking-reliability-2idykp32g) · Cast AI · 0 upvotes · 0 comments - [Node.js 20\+ memory management in containers](https://daily.dev/posts/node-js-20-memory-management-in-containers-ijekik8r4) · Red Hat Developer · 18 upvotes · 0 comments --- Tags: [#kubernetes](https://daily.dev/tags/kubernetes), [#java](https://daily.dev/tags/java), [#jvm](https://daily.dev/tags/jvm) [View this post on daily.dev](https://daily.dev/posts/java-jvm-cpu-and-memory-requests-and-limits-in-kubernetes-9pj5al4jr) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Java JVM CPU and Memory Requests and Limits in Kubernetes","url":"https://daily.dev/posts/java-jvm-cpu-and-memory-requests-and-limits-in-kubernetes-9pj5al4jr","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/java-jvm-cpu-and-memory-requests-and-limits-in-kubernetes-9pj5al4jr"},"datePublished":"2026-08-31T13:06:42.760Z","dateModified":"2026-08-31T13:07:08.660Z","description":"A deep technical breakdown explains why sizing a JVM inside a Kubernetes container requires coordinating four coupled decisions: container memory limit, heap...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6f04d5d2de18f50ebea8fed154c0e8e4?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/6f04d5d2de18f50ebea8fed154c0e8e4?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"LearnKube","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"LearnKube","logo":"https://media.daily.dev/image/upload/t_logo,f_auto/v1/logos/90786df1b5d44abb91a090a0b6c81517","url":"https://daily.dev/sources/learnkube"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/java-jvm-cpu-and-memory-requests-and-limits-in-kubernetes-9pj5al4jr","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":3},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"kubernetes,java,jvm","timeRequired":"PT21M"} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"LearnKube","item":"https://daily.dev/sources/learnkube"},{"@type":"ListItem","position":3,"name":"Java JVM CPU and Memory Requests and Limits in Kubernetes"}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/java-jvm-cpu-and-memory-requests-and-limits-in-kubernetes-9pj5al4jr#faq","mainEntity":[{"@type":"Question","name":"Why does my Java pod get OOMKilled by Kubernetes even though the JVM never threw an OutOfMemoryError?","acceptedAnswer":{"@type":"Answer","text":"A JVM in a container has two separate memory boundaries: the Java heap, capped by -Xmx or MaxRAMPercentage, and the container's total memory, capped by limits.memory. The container limit covers the heap plus metaspace, code cache, thread stacks, direct buffers, GC structures, and native libraries. If total memory hits that limit first, the kernel kills the process before HotSpot can report a heap OutOfMemoryError, and Kubernetes reports the reason as OOMKilled. Track how memory boundaries interact when debugging container crashes on daily.dev."}},{"@type":"Question","name":"How much container memory should I leave outside the JVM heap when setting -XX:MaxRAMPercentage in Kubernetes?","acceptedAnswer":{"@type":"Answer","text":"Leave enough room for thread stacks, metaspace, code cache, direct buffers, and GC structures beyond whatever percentage of the container limit the heap uses. In one 512MiB example, setting MaxRAMPercentage=50.0 gave a roughly 247MiB heap, leaving about 256MiB for everything else; in a 256MiB container, a 50% target left about 133MiB outside the heap, which was enough to avoid an OOMKilled process, while a heap sized to the full limit was not. Developers tuning JVM heap percentages against container limits can compare notes on daily.dev."}},{"@type":"Question","name":"Does a Kubernetes CPU limit affect Java garbage collection pause times?","acceptedAnswer":{"@type":"Answer","text":"Yes, a lower CPU limit can make garbage collection pauses noticeably longer. In one comparison, cutting the CPU limit to half a CPU caused the container to hit its quota during collection cycles, so the cgroup throttled and the collector had to wait for the next quota period; reported GC collection time rose from 82ms to 331ms and average System.gc() latency rose from 2ms to 18ms in that test. Anyone sizing CPU limits for latency-sensitive JVM workloads can dig into these trade-offs on daily.dev."}}]} ```