Repository navigation
Conversation
…processes per release Control state's maps are now imbl OrdMaps. Cloning the published state shares its structure, and the commit diff skips shared subtrees, so a commit costs in proportion to the rows it touches rather than to the whole state. Stamping visits only the rows written with a pending generation, since committed state never names one. Code that changed many rows in place now changes only the rows it selects. A release may run up to 256 processes, so one release seats up to 32,768 players at 128 per process. The bench fixture allows 64 processes. Refs #49, #155
This branch has not been deployed
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.
Refs #49, #155. A 5,000-player environment had two control-side blockers:
Commits now scale with the rows they change
Stateis animbl::OrdMap(MPL-2.0, allowed bydeny.toml). Copying the state at the start of an update shares structure, so it costs almost nothing.OrdMap::diff, which skips shared subtrees.method_sequence. Committed state never holdsGeneration::PENDING, so every row that names it differs from the previous state and goes throughWrites::pending.state::modify, which changes only the rows it selects.Up to 256 processes per release
chunk_control::MAX_PROCESSESis 256.Release::validateand managed environments both use it, so a release can seat up to 32,768 players. chunk-build'slocal.max_processesallows the same.Benchmarks (4 pinned CPUs, two runs per point, main 7a1f97a vs this branch)
At 5,000 claims the branch still sustains 20/s churn and 100/s population, with no failures. The machine was shared, so the first pair of runs is the noisiest.
Breaking: existing deployments recorded
max_processes = 32. If core has to rebuild one of them after this upgrade, for example a replacement core restoring its database without the archive, control rejects it asrelease configuration changed. The fix is to deploy again. Pre-release, so there's no migration.Next limits for #155, not changed here
jvm::topic::deliveries, which scans every claim on each host-topic update, so CPU per operation still grows with population (about 54 → 65 ms).Checks
cargo test -p chunk-control(92),cargo test -p chunk-environment managed::(43), chunk-build project tests (9), chunk-bench config.cargo deny check licenses.🤖 Generated with Claude Code