Repository navigation
Conversation
Merging this PR will not alter performance2 warnings
Comparing Footnotes
|
This was referenced Nov 17, 2026
Integrations can report p1 to p99 of the time per iteration in `stats.percentiles_ns`. The field is optional: results files without it keep parsing, and it is left out of the JSON when absent. Refs COD-4241
fargito
force-pushed
the
feat/walltime-percentiles
branch
from
November 18, 2026 14:39
322d73b to
76030c0
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
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.
Add an optional
percentiles_nsfield to the walltimeBenchmarkStats: p1 to p99 of the time per iteration, in nanoseconds like the other_nsstats.Integrations already hold every round in memory but only report min, max, mean, stdev and quartiles. Reporting the full percentile set lets the backend keep the shape of each benchmark's distribution.
The field is optional and skipped when absent, so results files from current integrations keep parsing, and exec-harness keeps writing the same JSON.
Refs COD-4241