Repository navigation
[benchmarker] Add separated_ops.jsonnet - #1784
Merged
Merged
Conversation
BenjaminPelletier
marked this pull request as ready for review
October 8, 2026 11:41
barroco
approved these changes
Oct 8, 2026
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.
This PR makes progress on #1724 by adding a separated_ops.jsonnet benchmarker configuration reflecting the intent of one of the remaining two identified performance scenarios. Commonalities are factored out of congested_area.jsonnet and both configurations are migrated to user_search rather than user_ramp for increased likelihood of success with default parameters.
The results below are likely not reflective of actual performance because they were produced on my poor laptop with interruptions, but I think they suggest these two scenarios are valid: