Simplify benchmark schemas and routes #387
Merged
Conversation
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
WillEngler
approved these changes
Dec 9, 2025
Contributor
WillEngler
left a comment
WillEngler
left a comment
There was a problem hiding this comment.
Love to see a net red PR!
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.
Overview
This PR sets up the backend for the new benchmark setup. I removed all of the job tracking and complex setup leaving a single 'BenchmarkResults' table that tracks basic information about a benchmark run with a JSON field for
metricsmeaning we can adjust the metrics we capture without changing the database schema. This setup allows us to implement more benchmarks in the SDK and only need to hit thePOST /benchmarksto publish a run no matter what the benchmark is or what the metrics it sends contain. The frontend can hitGET /benchmarksto pull down data to populate the leaderboard.The
POSTroute for publising benchmark results is limited to use by super users only.Testing
Updated unit tests.