-
Notifications
You must be signed in to change notification settings - Fork 156
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
Crossing boundry between units in a single graph #15
Comments
I have an idea, which could be to use math.js to convert what ever future values back to the right unit, This could be broken down into 2 tasks:
|
This is a bit messy right now but ive got it working here: Example of it working here (on the bottom graph highlight the third node it should be in ns): |
Thank you for the work. Let me take a look after Criterion.rs support has landed. |
Normalising the units when filling the datasets, ie. to seconds, also does the trick, unless you care that much about being as accurate as possible.
|
Hey @rhysd , great work on this.
Is anything supposed to happen if some data crosses the boundry between say nanoseconds and microseconds?
In my benchmark here that has happened in the bottom two:
https://jasonwilliams.github.io/boa/dev/bench/
It looks like its become a lot slower, but actually it sped up from 1 us to 900 ns.
Unfortunately once the chart is made with a unit im guessing its fixed.
think i answered my own question
https://github.com/rhysd/github-action-benchmark/blob/master/src/default_index_html.ts#L198
The text was updated successfully, but these errors were encountered: