-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: Benchmarking without a reference? #5
Comments
no that's not currently supported. Just so I understand, would you run all the benchmarks with no comparison function? You're only interested in min, max and mean? I could change the code to look at the length of the tuple and not run a comparator test if there isn't a second benchmark defined. It would get tricky if some did and some didn't (with the table output) |
Yes that would already suffice (perhaps trimmed mean / median). What I had in mind is a workflow as offered by frameworks like e.g. This internal diffing isn't super important though, because a lot can already be achieved by doing manual before/after or snapshot runs. Thanks to the beautiful output in the form of a table, once could for instance simply take the output and append it to some |
ASV (airspeed velocity) might suit your requirements, it has a database, web UI and a ton of other tools. Some big data science libraries (iirc Pandas inc) use it. |
Yes indeed, ASV is pretty nice! In certain use cases something more lightweight like rich-bench is a nice alternative though due to its simplicity. |
Reading the documentation made me wonder why the
__benchmarks__
entries are tuples with two functions a and b. Apparently this assumes that a benchmark always has to be performed against some kind of reference?I'm wondering if the framework can be easily adapted to use cases where one doesn't have such a reference function. Say, I just to benchmark
sort_three
without the kind of arbitrarysort_seven
reference.Is this already supported somehow?
The text was updated successfully, but these errors were encountered: