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
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.
Benchmarking with a JIT compiler is a massive PITA.
Long benchmarks take an absurd amount of time, short benchmarks are noisy and still take significant time. I don't want to run benchmarks for all loggers all the time, instead I want one long run with consistent results for all loggers, and then update Clip results as I iterate on it. If I decide to add or change the benchmarks I can rebuild the database from scratch.
This database file is later used to produce docs, charts and PDFs. It can also be seeded from historical benchmark artifacts.
Did some drive-by refactoring: migrated from venv + black to uv + ruff, updated/revised the feature matrix.