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

Limit concentrations of client requests to spread out server load #57

Open
wizkid057 opened this issue Jan 6, 2025 · 0 comments
Open
Assignees
Labels
enhancement New feature or request

Comments

@wizkid057
Copy link
Collaborator

Server side load gets momentarily concentrated unnecessarily for several rounds of template updates after a network block change.

The network block change load is expected (currently... future enhancements may make this a non-issue). However, with many users on the default work update interval there continue to be load spikes for several rounds of work updates concentrated around the default work update value.

These concentrations continue until they eventually diverge naturally, or until there's a new network block.

Probably something as simple as a random -5,000 to +5,000 millisecond delay delta on the first work update after settling in on a new network block full work would be sufficient, provided the random value is executed with sufficient temporal resolution.

To be clear, this doesn't adversely affect anything currently, but an enhancement to help with future server side capacity scaling is certainly best long term.

@wizkid057 wizkid057 added the enhancement New feature or request label Jan 6, 2025
@wizkid057 wizkid057 self-assigned this Jan 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant