Replace markdown result files with CSV + JSON output#46
Merged
Conversation
snichme
approved these changes
Apr 30, 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.
WHY are these changes introduced?
Markdown was a poor storage format for benchmark results: parsing required fragile regex, aggregation logic (medians) was duplicated between bash and Python. Moving to CSV + JSON separates raw measurements from metadata, lets
aggregate_results.pycompute statistics directly, and makes the data easy to process with standard tools.Reference: #43
WHAT is this pull request doing?
The benchmark scripts (run_multiple_latency_tests.sh, run_multiple_throughput_tests.sh) now write two files instead of one markdown file:
aggregate_results.pyis updated to read these CSV+JSON pairs and compute medians using statistics.median.HOW was this pull request tested?
Small test run: #50