Repository navigation
Cap players at 5 and spend the headroom on view distance - #74
Merged
Merged
Conversation
MAX_PLAYERS 20 -> 5. Five is the real population: known family members on an enforced whitelist. 20 was typed, never measured and never tested. A slot only costs memory while someone is in it, so the worst case is what the box has to be sized for, and capping at the real population cuts that worst case by three quarters on the same 4 vCPU / 8 GB droplet. That headroom is spent on how the world looks. VIEW_DISTANCE 12 -> 16 and SIMULATION_DISTANCE 8 -> 10. Loaded chunks scale with the square of view distance: 20 players at 12 was up to 12,500 chunks, 5 players at 16 is at most 5,445, still under half the old worst case. 16 is where Terralith's terrain reads as scenery instead of fog. Simulation 10 is the vanilla default, so farms and Create contraptions tick at normal range. Resource limits (cpus 3.5, mem_limit 6.5g, 5G heap) are untouched: the droplet stays s-4vcpu-8gb. Every cheaper plan either halves RAM, which this pack cannot take, or costs more than $48 for 4 vCPU. The known cost is worldgen bursts while someone explores new terrain, which spark will show as tick spikes. The fix for that is chunk pre-generation against a stopped world, not lowering this again.
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.
What
MAX_PLAYERSVIEW_DISTANCESIMULATION_DISTANCEResource limits and the droplet plan are untouched (
s-4vcpu-8gb, $48).Why
Five is the real population: known family members on an enforced whitelist.
20 was typed, never measured and never tested. A slot only costs memory while
someone is in it, so the worst case is what the box has to be sized for, and
capping at the real population cuts that worst case by three quarters on the
same hardware.
That headroom is spent on how the world looks. Loaded chunks scale with the
square of view distance: 20 players at 12 was up to 12,500 chunks, 5 players
at 16 is at most 5,445, still under half the old worst case. 16 is where
Terralith's terrain reads as scenery instead of fog. Simulation 10 is the
vanilla default, so farms and Create contraptions tick at normal range.
Cost and how to see it
Worldgen bursts while someone explores new terrain, visible in spark as tick
spikes. The fix for that is chunk pre-generation against a stopped world, not
lowering this again.
Validation
docker compose configvalidates; test_world_not_tracked,test_world_no_player_data, test_client_server_mods, test_custom_mods_reviewed,
test_kubejs_script_hazards, test_security_alerts and test_design_role.js pass.
Touches no
data/world/path.Note: merging restarts the container, so merge when nobody is playing.