feat: tac_bench with sqlite database support #995
Draft
Conversation
This file contains 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
This allows us to run benchmarks and serialize data into a sqlite database, thereby providing support for finer grained SQL queries, as well as eliminating future parsing boilerplate.
|
Alive Statistics: 90 / 93 (3 failed) |
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.
Due to the spectacular success I've had with using sqlite to write crash tolerant, easy to use, and trustworthy benchmarking code, we perform the same replacement for
tac_bench, where we write a variant,tac_bench_sqlite "path/to/db" ["benchmark_name" : "tactic",*]as the syntax for creating a sqlite DB and writing data into it.