Repository navigation
feat(server): --memory-mib caps a process and derives its budgets - #4
Merged
Merged
Conversation
GentBajko
marked this pull request as draft
November 15, 2026 00:12
Member
Author
|
Converted to draft: Arda's feature process needs the maintainer's approval of this change's plan before code, and that approval has not been given. The code here was written ahead of it. The maintainer can approve the plan as built (review this PR and mark it ready) or ask for the plan to be redone first. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
For DiceMaster. Its plan is three
arda-serverprocesses on one 16 GB, 8-core Arm box beside about 1.5 GiB of its own processes. Today the server admits a worst case of 14.6 GiB.The setting
--memory-mib <MiB>, orARDA_MEMORY_MIB(the flag wins; the image's default entry reads the env var). Without either, nothing changes: a 16,384 MiB ceiling and every default.crates/arda-server/src/ceiling/mod.rs). The derived budgets are:--area-cache-mib,--fine-cache-mib,--max-connectionsand--bake-result-mibkeep their values when given.PipelineLimits.Measurements
Ryzen 9 9950X3D, release build, placeholder library, prefetch on, baking off, every request at 64 px per square. The workload is a 150-cell walk: open a cell (JSON with scene and rules), read 12 view tiles, prefetch the ring, step to a prefetched neighbour. Then the same walk again.
413 payload_too_large;Not reached: about 4.5 GiB for a full-size world
society/parsed at twice its size 773, shore 85, largest town plan 462) and the floors 4,098 MiB.society/at twice its size.Evidence
ceiling::tests:world_api/ceiling.rs:cargo fmt --checkandcargo clippy --workspace --all-targets -D warningspass.cargo test --workspace --all-features --releasepasses (contract kit andworld_apiincluded).Docs
API.md(the flag row and § Memory ceiling),logic/16§api-memory,07-operations.md,open-items.md(OI-65, OI-66),CHANGELOG.md(Unreleased), the ledger, and a comment intools/docker-entrypoint.sh.Process note
The user was away, so spec and plan were written from the DiceMaster session's brief without the approval gates; this PR is the gate.
CHANGELOG.mdanddocs/capstone/changelog.mdwill need a trivial conflict resolution against #2 and #3.