Skip to content
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

Ability to set a "reference" job #179

Open
michalmuskala opened this issue Feb 19, 2018 · 2 comments
Open

Ability to set a "reference" job #179

michalmuskala opened this issue Feb 19, 2018 · 2 comments

Comments

@michalmuskala
Copy link
Contributor

Right now when benchmarks are compared, they are always compared to the fastest run. I think it would be useful in some situations to set a "reference" run and compare all the other runs to that.

One example would be the benchmark suite of jason, where I'd like to see all the other encoders reported relative to Jason itself, even though jiffy is the fastest most of the time. Right now, I have to do the additional computations manually, to get the desired numbers, that I can use to annoy people convincing them how fast Jason is 😉.

@michalmuskala
Copy link
Contributor Author

I looked into what could be the best way to do this and I'm not really sure. Right now, it seems, the order is handled by each formatter separately. Should we also move that to be done in just one place at the same time? We'd probably need to pass two things in that case - the ordered scenarios + the base scenario, so the comparison can be easily computed by the formatter.

@PragTob
Copy link
Member

PragTob commented Mar 13, 2018

@michalmuskala yes that's exactly how I'd like it to be done :) I think right now through the memory vs. runtime split there's a bit of duplication/things that we need to unify or should generalize in general :)

PragTob added a commit that referenced this issue Jul 7, 2024
Basis is from #281 which we let lie for too long, sorry.

Also too much had changed in the mean time (`RelativeStatistics`)
so reopening it didn't make a ton of sesnse.

Fixes #179
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants