M
Michal Vaner
vorner.github.io · Personal blog · on HN since 2018
Michal Vaner is a Rust developer who writes about async performance, POSIX APIs, ergonomics and library internals like arc-swap.
What HN saysHN links it for his async benchmark, which commenters discuss, with one asking for newer hardware results since the tests were run on old machines.
18HN people shared it
2linked it in comments
27stories submitted
1.0Kstory points
6 months agolast shared
2018people per year2026
Most-shared posts
- 140 millisecond bug3 people · 126 points · first shared 2020 · 26 comments on HN
- 2Dark Side of Posix APIs3 people · 98 points · first shared 2021 · 23 comments on HN
- 3Throw away code2 people · 101 points · first shared 2020 · 79 comments on HN
- 4Saving Some Allocations2 people · 3 points · first shared 2021 · discussion on HN
- 5Tricks in Arc Swap (2019)2 people · 2 points · first shared 2024 · discussion on HN
- 6Async bench2 people · first shared 2019
- 7Why is Rust difficult?1 people · 309 points · first shared 2018 · 254 comments on HN
- 8Dark side of ergonomics in Rust1 people · 178 points · first shared 2018 · 130 comments on HN
- 9Performance experiments with matrix multiplication in Rust1 people · 97 points · first shared 2018 · 24 comments on HN
- 10Mental models around Ok-Wrapping1 people · 83 points · first shared 2020 · 48 comments on HN
- 11Rust in Avast1 people · 4 points · first shared 2019 · discussion on HN
- 12Rust: Fighting the Async Fragmentation1 people · 3 points · first shared 2019 · discussion on HN
- 13Personal Collection of Rust Hacks1 people · 3 points · first shared 2019 · discussion on HN
- 14Should you learn Rust?1 people · 3 points · first shared 2018 · discussion on HN
- 15Making Rust Arc more atomic1 people · 3 points · first shared 2018 · discussion on HN
What HN people wrote when they linked it
arve0 · 2019-01-22
How much performance is gained by going async instead of blocking threads on modern hardware?
Skimmed through https://vorner.github.io/async-bench.html. If I understand it correctly, one get about twice the performance with async.
Is this correct? Seems like a compromise (code complexity vs performance) not worth taking.
tcfhgj · 2026-04-26
hardware from 10 years ago - do you have benchmarks for more recent hardware?
https://vorner.github.io/async-bench.html