You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Align the Minecraft Java memory request with its default fixed JVM heap and native working set #71
At catalog a660997c the Minecraft Java template requests 2 GiB of memory, limits the game at 4 GiB, and auto-sizes both initial and maximum heap to 75% of that limit. With empty heap overrides the calculated heap is 3 GiB before native memory and sidecar costs. The scheduler uses the lower request. Under load, packing multiple such servers can consume node headroom that looked available for another game or backup.
Reproduction
Render a default Minecraft Java GameServer, inspect the game container requests/limits and the resolved INIT_MEMORY/MAX_MEMORY. Then run representative populated worlds on a constrained worker and measure steady-state and startup working sets, GC pauses, CPU throttling and tick latency. The configuration mismatch was verified in source. Eviction frequency and an appropriate production size still need measurement.
Acceptance criteria
Give the default tier a measured memory reservation coherent with its initial heap plus native headroom, or adjust/document the heap policy so that the baseline tier is internally consistent.
Verify partial resource overrides and explicit heap settings on new and existing servers. Surface a configuration whose requested working set exceeds the scheduling reservation.
Publish the observed working set and tick latency for the qualified tier with a neighboring cold start or backup. Preserve explicit custom tiers.
Activity