Nikolai Vazquez

This might be a bit of work on your end, but could you please check if the same happens with Criterion?

I'm not able to reproduce your results when I don't add `memcache` or `mimalloc`. I can try again later with those added. Also, you can use `NUM_ITEMS` directly since `usize`...

This is a bit of a nuanced issue. Currently benchmarks don't have any statistics outside of min/max/median/mean time. But I would very much like to do proper statistical analysis across...

Are you suggesting in this case that Divan would discard the first 10 samples after it finds a proper sample size? Perhaps we could have something like: ```rs #[divan::bench( //...

@epage I suspect that each benchmark harness is going to want to run things its own way and thus enforcing a single canonical format across the entire ecosystem might be...

I'm curious what the new `samply record` graphs look like after this change.

I'm not a fan of relying on `Drop` for this to be safe. I would rather this be modeled like scoped threads where the lifetimes associated with the scope prevent...

I haven't had time to think much about custom counters (planned), so I'm curious how you think `Ratio` should be displayed? I know how `Bencher::output_counter` could be implemented, so that...

I plan to support async functions and have some code in progress for it. This will likely come soon after allocation profiling. It wouldn't be until after or during the...

Update: I now have an implementation of allocation profiling in https://github.com/nvzqz/divan/pull/40. So maybe a week after that lands I'll get around to finishing async support.