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

Increase default emerge queue limits and limit enqueue requests for active blocks. #10616

Merged
merged 1 commit into from Nov 12, 2020

Conversation

lhofhansl
Copy link
Contributor

@lhofhansl lhofhansl commented Nov 8, 2020

Partially related to #10597

The visual view cone of a player could be up to 2400 blocks.
The current emerge queue limits are 64 for disk reads, 64 for block generate, and 512 for a server in total.
Thus the queues would full over and over before the blocks have been loaded.

Even before #10597 these were quite low. This PR doubles these values - I would consider even that very conservative (I have certainly set mine much higher, but we have to start somewhere).
Note that these settings only increase the server's ability to queue requests, and hence to pace its work better.

I will renew my call to please reduce the "insane" number of config options.
@paramat Do need both a disk and generate queue limit (again this is not a work limit, but a queue limit)? When would I set these differently?

Edit: In return block requests on behalf of ABMs are limited to 1/2 of the total (as is, ABM requests can starve out the loading of visible blocks)

@paramat
Copy link
Contributor

paramat commented Nov 9, 2020

Do need both a disk and generate queue limit (again this is not a work limit, but a queue limit)? When would I set these differently?

I do not understand the emergequeue limits, sorry. So i am unable to review this PR.
Perhaps discuss with another core dev or celeron55 (he is likely to respond within 24 hrs. if you mention him in a message on IRC dev channel).

@paramat paramat removed their request for review November 9, 2020 13:56
@lhofhansl
Copy link
Contributor Author

Could people try to jack up these values and see what happens?

For my local server I have all these multiplied by 10(!), and things are (much) faster with no detriments (that I could discern).
Increasing these queues does not necessarily cause more work on the server, but allows it to smooth things out by ... well ... queuing.

@lhofhansl lhofhansl changed the title Increase default emerge queue limits. Increase default emerge queue limits and limit enqueue requests for ABMs. Nov 9, 2020
src/emerge.cpp Outdated Show resolved Hide resolved
@lhofhansl lhofhansl changed the title Increase default emerge queue limits and limit enqueue requests for ABMs. Increase default emerge queue limits and limit enqueue requests for active blocks. Nov 11, 2020
Copy link
Member

@sfan5 sfan5 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Fine by me

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

Successfully merging this pull request may close these issues.

None yet

3 participants