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
@eddyb recently posted a fantastic PR to measureme adding support for instruction counts making use of the perf-event-open-sys crate, and has reported some very low-noise results using it for rustc benchmarks.
There are a few places to possibly get started, depending on ambition levels:
move my mega-old criterion fork to use measureme's counter
make a newer criterion fork that uses measureme's counter
move off of criterion and define our own bench runner which uses measureme's counters
(1) seems easiest, (3) is what I'd actually like to do given the difficulty of doing sound statistics with the summary stats reported by criterion. But that might be too ambitious for an initial outing.
The text was updated successfully, but these errors were encountered:
One of lolbench's main tricks is to use hardware performance counters in addition to wall time for detecting anomalies. I first implemented this using a fork of criterion which in turn makes use of a very MVP interface I wrote against perf_event_open.
Since then, https://lib.rs/crates/perf-event-open-sys was published and has apparently gotten quite mature!
@eddyb recently posted a fantastic PR to measureme adding support for instruction counts making use of the perf-event-open-sys crate, and has reported some very low-noise results using it for rustc benchmarks.
There are a few places to possibly get started, depending on ambition levels:
(1) seems easiest, (3) is what I'd actually like to do given the difficulty of doing sound statistics with the summary stats reported by criterion. But that might be too ambitious for an initial outing.
The text was updated successfully, but these errors were encountered: