Where memory and processor go.
WHAT A CONTAINER CONSUMES
Exactly what its process consumes, plus a little overhead.
WHY REPORTED FIGURES CONFUSE PEOPLE
Tools inside the container may report the host's resources, not the limits.
WHAT THAT CAUSES
Runtimes sizing themselves for the host and being terminated.
WHERE THAT BITES HARDEST
Language runtimes choosing heap sizes and thread pools automatically.
WHAT TO DO
Use recent runtime versions, which respect container limits Or set the limits explicitly in the application
WHAT TO SET FOR MEMORY
A limit, always, with headroom above observed peak.
WHY HEADROOM
Exceeding it terminates the container without warning.
WHAT TO WATCH
Termination events for exceeding memory.
WHAT THEY INDICATE
A limit too low, or a leak.
HOW TO TELL WHICH
Whether usage grows steadily or spikes.
WHAT PROCESSOR LIMITS DO
Throttle, rather than terminate.
WHAT THROTTLING FEELS LIKE
Latency, with no obvious cause.
HOW TO SEE IT
Throttling metrics, which most people never look at.
WHAT TO BE CAUTIOUS ABOUT
Tight processor limits on latency-sensitive services.
WHAT TO MEASURE BEFORE SETTING ANYTHING
Actual usage under realistic load.
