You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It’d be nice to for instance show the average time in milliseconds if a benchmark is slower or write something to the effect of “80.9 Million” iterations per second for the console output for a fast benchmark.
It'd be important to me this auto scaling takes into account all results. I.e. I always find it harder to compare when results are reported in different units so either the values of (for instance) all averages are scaled to the same unit/magnitude or none are.
The text was updated successfully, but these errors were encountered:
I was just doing something similar with unit formatting in an app I'm working on, and I saw your recent tweet. I would love to contribute to this issue since I'm in thinking about it. Would you like me to start in on this, and we can work through the details as we go?
Any other considerations you want to think about ("M" vs "Million", etc)?
M/Million, B/Billion was definitely something I was thinking about, although I often find it to be somewhat confusing but Million/Billion is long. So I'm torn. I was also thinking about doing iterations/100ms or iterations/1ms instead but think it might be even more counter intuitive.
In a later step (just as a hint) I think I'd also want to turn on/off auto scaling (like other options), but that's easily/gladly another PR.
As always (or back in the days :) ), glad for early PRs, reviewing and working it out as we go :)
It’d be nice to for instance show the average time in milliseconds if a benchmark is slower or write something to the effect of “80.9 Million” iterations per second for the console output for a fast benchmark.
It'd be important to me this auto scaling takes into account all results. I.e. I always find it harder to compare when results are reported in different units so either the values of (for instance) all averages are scaled to the same unit/magnitude or none are.
The text was updated successfully, but these errors were encountered: