Skip to content

Align the Minecraft Java memory request with its default fixed JVM heap and native working set #71

Open

Description

@Baylem

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.

Game resources · Heap defaults. #8 introduced automatic heap sizing; #65/#66 and GameplanePanel/Gameplane#943 addressed settings and preview. GameplanePanel/Gameplane#875 addressed pool policy and quotas.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions