Split benchmarks into individual targets#1759
Merged
Conversation
Contributor
Author
This stack of pull requests is managed by Graphite. Learn more about stacking. |
This was referenced Feb 11, 2026
Merged
Contributor
Author
|
The stack can be validated by looking at the final Claude hunt results here: https://drive.google.com/file/d/1mbgFAFuC5s2HwM3IhoNCgqZcmt7Ho7a2/view?usp=sharing |
5485811 to
fe00bff
Compare
blt
approved these changes
Feb 13, 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
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.

What does this PR do?
Restructures the benchmarking system for
lading_payloadby:default.rsbenchmark entry point into individual standalone benchmarkscriterion_main!to each benchmark file to make them independently runnableMotivation
This change improves the developer experience by:
Additional Notes
The benchmark structure now follows a more modular approach where each payload type has its own dedicated benchmark file with appropriate measurement times. This makes it easier to run specific benchmarks during development and reduces the overall time needed for benchmark execution.