New benchmarking scripts (Spring 2025) #29
Draft
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
ulysses4ever
changed the title
Collaborator
Author
|
I'm now of the opinion that insterad of a quick and lacking re-implementation of Criterion that this code is, we should instead just use The second script (sweep_seq.py) actually does something new: it runs benchmarks on arrays of varying sizes. The issue is that I don't understand what methodology it employs for picking sizes. If I ask an LLM what sizes to pick, I get a lengthy answer with the gist being: |
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.
spinoff from #22
This code needs examples, which, hopefully, could be run in CI for sanity checking (not for real numbers).