criterion.rs VS message-io

The three popular options for benchmarking in Rust are: libtest bench, Criterion, and Iai.

Holy crap. I was just writing a blog to complain about the state of Rust benchmarking and I think this might address most of my points. The biggest one is the ability to have benchmarks collocated within the library like tests which is the biggest annoyance.

It’s also nice to see that it can report multiple counters in parallel. I put up a similar feature[1] for criterion recently but I fear the project isn’t being maintained anymore…

Haven’t looked deeply into divan yet but the other requirements I have for criterion’s power is to run tests with statistical guarantees on the results, terminate quickly when statistical significance is reached (—quick), provide a comparison of the delta from a previous benchmark, and to run async code. Wonder how this stacks up.

[1] https://github.com/bheisler/criterion.rs/pull/722

criterion for benchmarks,

For an extra optimization, you might look into techniques like branchless code, turning array of structs into struct of arrays for better cache utilization/lowering branch mispredictions. There is many talks on YouTube how to actually measure and improve performance of native code. And for rust there is a criterion.rs for benchmarking.

https://github.com/bheisler/criterion.rs is good for tests like that. It will give you much more than a single number and handle things like outliers. This makes identifying noisy tests simpler.

I have tried many ways but I think is not possible. I put it on https://github.com/bheisler/criterion.rs/issues/631.

Criterion is still the gold standard.

Pros for Criterion over the stdlib: https://github.com/bheisler/criterion.rs#features

Downsides of Criterion: https://bheisler.github.io/criterion.rs/book/user_guide/know...

message-io: a networking library meant to be very simple, built on mio.

Another one I know about, but have not looked into yet, is message-io.

I'm working in a transport network library that possible fits as a building block for yours and solves the problem of using different underlying transports: message-io

Here is benchmarks

I think https://github.com/lemunozm/message-io can be a good candidate.

The idea behind message-io is not to populate a current transport with a lot of options/profiles/modifications... this obfuscates the default way of working with it. Instead, if you want to build some behaviour on top of it, it is as easy as making an adapter! Following this pattern, you can split the way of using the library from the behaviour of the transport, keeping the things simple.

The initial purpose was to show the capabilities of https://github.com/lemunozm/message-io Nevertheless, Termchat is growing and needs to polish some of its features. At this point it is not for real-world use but I hope to reach this target.