Repository navigation
Report the median of several benchmark runs - #27
Merged
Merged
Conversation
run.sh now runs each store RUNS times (default 3), alternating them, and the report shows the median per workload with the range next to it. Results only count as agreeing when every run of both stores matches.
venkat1701
force-pushed
the
feat/bench-median-of-runs
branch
from
October 4, 2026 08:27
b9a457a to
f02c2b6
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
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.
Closes #13
benchmarks/run.shnow runs each storeRUNStimes (default 3). Each pass alternates HStore and HyperGraphDB, so a slow stretch on the machine hits both rather than one. Every run is saved as<store>-<n>.json.The report groups the files by store and shows each cell as the median with the slowest and fastest run in brackets, e.g.
14,233 ops/s (12,717 to 15,748). The ratio column is now the ratio of medians. "Results agree" only says yes when every run of both stores returned the same checksum.While in there I replaced the em dash between the workload id and its description with a colon.
I checked the report against two existing runs per store. I didn't do a full three-run comparison, since the machine is loaded right now and the numbers would be misleading; that's better done on a quiet box before updating
docs/benchmarks.md.