iai VS essie-tls-rs

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

Iai^1 uses CacheGrind^2 to count instructions

[1] - https://github.com/bheisler/iai

But, /u/bencherdev, please consider integrating iai measurements! By the same person behind criterion but designed for one-shot measurements that are stable in CI measurements.

Is lai no longer maintained? It hasn't had any commits in a year and a half.

Lately I've found that using unwrap_unchecked has nearly zero performance gain but all the UB to gain if you change the code one day. My source is iai which provides exact instruction counts and is entirely deterministic for any given execution (and almost-deterministic across different compilations of the same program).

Have you tried criterion.rs or iai ? The first is great at micro benchmarks and, if it is not enough, the second can catch even smaller performance difference.

In the mean time maybe https://github.com/bheisler/iai could be of help

Well, the most interesting one is probably Iai; an experimental benchmark framework that runs all of the benchmarks in Cachegrind for much higher precision and repeatability than is possible with Criterion.rs. It's still a work-in-progress, so I haven't published it on Crates.io yet. See the readme for a more detailed discussion of the pros/cons relative to Criterion.rs.

This week I started writing a safe TLS library for it, called Essie TLS. I read a lot and found that constant-time Rust code requires unsafe. So my plan is to use a delay timer to avoid leaking secrets via timing side-channels. This will make TLS handshakes a little bit slower. Writing a TLS library is a lot of work. TLS 1.3 is very complicated and spans about 200 pages of RFCs. But the tools are working very nicely: Rust stable, CLion, and Gitlab.com.