Benchfmt.rs: Bringing Go's benchmarking and benchstat workflow to Rust
witcher
29 points
7 comments
November 04, 2026
Related Discussions
Found 5 related stories in 129.8ms across 11,645 title embeddings via pgvector HNSW
- GPU Offload in Rust: Portable, Safe, and Fast linggen · 185 pts · August 17, 2026 · 56% similar
- The case to BYOB: build your own (coding) benchmarks oaa36 · 11 pts · September 10, 2026 · 55% similar
- How to speed up the Rust compiler in September 2026 trickypr · 242 pts · October 01, 2026 · 55% similar
- Async Rust vs RTOS showdown (2022) kooi · 71 pts · September 02, 2026 · 55% similar
- Rust Glancer: Rust LSP using 100x less RAM matklad · 103 pts · August 21, 2026 · 55% similar
Discussion Highlights (4 comments)
tsenart
At last someone does this!
lamaquina
Wow this is sweet
jauntywundrkind
I just keep asking the agent to throw `hyperfine` and or /`criteron` at things and hoping it's enough. Not a super clear sell here, to me, coming from this position of ignorance. I'd love to have better background, to compare, to know more. I'll try and see, I guess! This at least sounds not so bad: > I built benchfmt.rs, a zero-dependency Rust benchmark runner with a thread-local heap allocation counter, pprof profiler integration, and the same CLI flags as go test -bench. For those who don’t trust a new benchmarking runtime (you shouldn’t from the start!), it also ships a Criterion and libtest converter that emits Go’s benchfmt format directly.
syntacticsalt
As far as I could tell, benchstat seems to implicitly make a location-shift assumption in its interpretation of the Mann-Whitney U test, and I don't see why that assumption would hold.