Config Option - Only Render Territories Upon Startup #1768
Merged
Conversation
This file contains 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
renbinden
approved these changes
Jan 2, 2024
dmccoystephenson
deleted the
config/only-render-territories-upon-startup
branch
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.
Problem
Rendering territories is causing a lot of lag for some servers.
Solution
This PR introduces a config option to prevent the rendering of territories after the initial startup of the server. This limits the lag spike to one instance per session.
Testing
This was used by a server owner in the community and their TPS improved from 15 to 18. This seems to ease the lag a bit.
Related Issues
closes #1767