Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

What's a good setting for "asyncLoadConcurrency" when rendering the entire world #54

Open
GabrielSerealia opened this issue Sep 16, 2022 · 2 comments

Comments

@GabrielSerealia
Copy link

I'm trying to render a world with around 1.5 million chunks what would be an optimal setting for "asyncLoadConcurrency"? I currently have it set to 1000 but I don't know what's considered "too high" by the documentation.

@bergerkiller
Copy link
Member

The server will generally schedule that thing itself. For reference, when a player joins a server it instantly starts asynchronously loading all (10+10+1)^2 = 441 chunks when view distance is 10. If you were to use an async load concurrency of 441, it would mean its as if a player is spawning all the time every tick always keeping 441 chunks queued for loading.

The server will generally handle that fine, but it will cause other loads scheduled such as other players moving around/spawning to slow down.

I think 1000 is as far as you want to take it. Diminishing returns as the server throttles this anyway.

@GabrielSerealia
Copy link
Author

Hey, thanks for elaborating on how it functions! It makes a lot more sense now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants