Update the ThreadTransfer benchmark #210
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
This moves the consumer/releaser thread to a dedicated infra thread, instead of being part of an asymmetric benchmark. The releaser thread remains a singleton while the claim benchmark threads can be scaled to measure contention on the `Pool.claim()` call. Some blackholde CPU consumption has also been added, to place some realistic distance between the individual `claim()` calls. This is another vector for scaling contention up or down.
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.
This moves the consumer/releaser thread to a dedicated infra thread, instead of being part of an asymmetric benchmark. The releaser thread remains a singleton while the claim benchmark threads can be scaled to measure contention on the
Pool.claim()call.Some blackholde CPU consumption has also been added, to place some realistic distance between the individual
claim()calls. This is another vector for scaling contention up or down.