Repository navigation
test(bench): compare executor policy bookkeeping - #155
Merged
Merged
Conversation
Add a bounded Block versus DropNewest TaskExecutor batch probe with an oversized queue and zero-drop validation. Document it as a policy-branch signal rather than an attribution of individual private synchronization operations.
Interleave Block and DropNewest policy cases to reduce temporal bias and drain between every case. Validate completion and zero drops symmetrically, and document backend-specific policy semantics for the attribution probe.
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
1 participant
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.
Summary
Verification
This branch is stacked on the merged task-ownership profiling work from #154.