github-action-benchmark
github-action-benchmark copied to clipboard
support Cargo optional MB/s output
In a Rust benchmark, if you specify how many bytes a benchmark is touching, it can output MB/s. This parses and ignores that value.
Thank you for your contribution! Could you please add a test case with the MB/s unit that was failing and is passing now?
Maybe it would make more sense to support arbitrary units instead and extract the unit?
I have a test on this format that fails, for instance:
test cmov ... bench: 2835 cycles/iter (+/- 14)
test cmov2 ... bench: 2845 cycles/iter (+/- 19)
test mov ... bench: 1508 cycles/iter (+/- 17)
I added support for these changes in #280
resolved by #280