Direct answer
view-distance controls how far the server sends world chunk data around players. simulation-distance controls how far away game logic such as living entities continues to tick. Higher values can increase CPU, memory, network, and chunk-loading work.
How the settings differ
| Setting | Main effect | Common resource pressure |
|---|---|---|
view-distance | Chunks available/visible around players | Chunk loading, memory, network |
simulation-distance | Area where entities and game logic tick | CPU tick time |
A practical starting point
Do not lower values just because an optimization guide says “smaller is always better.” Start with the experience you want, measure the server, and reduce distances if chunk or tick load is a real problem. For a resource-constrained private server, values such as view distance 8 and simulation distance 6 can be a reasonable test point, not a universal requirement.
Change the values
view-distance=8
simulation-distance=6Restart the server after editing server.properties so the intended configuration is applied consistently.
Why player count changes the impact
Ten players standing together share many chunks. Ten players exploring in different directions create far more distinct loaded/generating areas. This is why the same distance setting can feel fine one day and expensive during exploration.
Profile before extreme changes
If the server still lags at reasonable distances, investigate entities, plugins, chunk generation, storage, and CPU tick time instead of reducing the world to an unnecessarily small radius.
Official references
These references were checked while preparing this guide. Version-specific behavior can change, so use the project documentation for your exact release when a detail differs.
Related guides
Help us improve this article
Tell us what is missing, unclear, outdated, or incorrect. You can also suggest something we should add.