benchmarks: add dedicated-consumer benchmarks for try_dequeue_from_producer#450
Merged
cameron314 merged 1 commit intoApr 28, 2026
Conversation
cameron314
reviewed
Apr 28, 2026
cameron314
left a comment
cameron314
left a comment
Owner
There was a problem hiding this comment.
Thanks, I think this makes sense overall.
benkier0
force-pushed
the
benchmarks/dedicated-consumer-dequeue
branch
from
April 28, 2026 12:58
2e83511 to
16cf73d
Compare
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Adds benchmarks for try_dequeue_from_producer and try_dequeue_bulk_from_producer —
two hot paths that had zero coverage despite being the fastest dequeue paths in the API.
Each benchmark pairs N/2 producers with N/2 consumers 1:1 and runs both the dedicated
path and general try_dequeue side by side so the scan overhead is directly visible.
Results (Apple M-series, 64-bit):
Note: the 16-thread "with tokens" result is higher than 8-thread — likely a scheduling
artifact from Apple Silicon's efficiency/performance core split.
Also relevant to #365.