weighted least reference count (wlrc) load balancing algorithm #15
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.
Same as lrc weight handling support pull request but implemented as separate algorithm. Reasons:
In practice wlrc gives us weighted algorithm that can handle misbehaving nodes (while wrr can't), so if someone is using nodes with different hardware specs than one node might have few times more memory and cpu cores, and so it can spawn much more workers. In such case lrc will probably forward more requests to it only when lower spec nodes are heavily loaded and they start to have longer response times (in theory, I didn't tested it).
Tested with ab -r -c 13 -n 13000 url, each node had number of workers equal to it's weight value. Results:
wlrc
lrc