Top all-time · #4205
Vorner’s random stuff
Personal blog · vorner.github.ioprogrammingsystems
Vorner’s random stuff is a personal blog at vorner.github.io about programming and systems. Since 2018, 18 different Hacker News readers have linked it 29 times, most often “40 millisecond bug”. The last post was in 2023, but the archive is still widely read.
Too few sampled comments (2) to say how often HN recommends it.?
Why HN links it
HN readers link this blog for its async-versus-blocking-threads benchmarks, which commenters cite when weighing async's performance gain against its code complexity. The comments are questions and citations, not judgements of the writing.
Summarised by Claude from a sample of 2 HN comments that link here. Each comment is marked recommending, critical or neutral (citing without judging); how this works.
Most-linked posts?
- 40 millisecond bug3 people · 3 mentions · first linked 2020-11-12
- Dark Side of Posix APIs3 people · 3 mentions · first linked 2021-01-09
- Saving Some Allocations2 people · 2 mentions · first linked 2021-01-31
- More tricks up in the ArcSwap's sleeve2 people · 2 mentions · first linked 2024-07-21
- /async-bench.html2 people · 2 mentions · first linked 2019-01-22
- Throw away code2 people · 2 mentions · first linked 2020-09-20
What Hacker News says?
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.
Comment linking /async-bench.html
on “Asynchronous Programming in Rust book”Submitted Why is Rust difficult? as a story · 309 points
HN discussionhardware from 10 years ago - do you have benchmarks for more recent hardware? https://vorner.github.io/async-bench.html
Comment linking /async-bench.html
on “What Async Promised and What It Delivered”Submitted Dark side of ergonomics in Rust as a story · 178 points
HN discussionSubmitted 40 millisecond bug as a story · 123 points
HN discussionSubmitted Throw away code as a story · 99 points
HN discussionSubmitted Performance experiments with matrix multiplication in Rust as a story · 97 points
HN discussionSubmitted Dark Side of Posix APIs as a story · 95 points
HN discussionSubmitted Mental models around Ok-Wrapping as a story · 83 points
HN discussionSubmitted Rust in Avast as a story · 4 points
HN discussionSubmitted Rust: Fighting the Async Fragmentation as a story · 3 points
HN discussionSubmitted Personal Collection of Rust Hacks as a story · 3 points
HN discussionSubmitted Making Rust Arc more atomic as a story · 3 points
HN discussionSubmitted Should you learn Rust? as a story · 3 points
HN discussionSubmitted Saving Some Allocations as a story · 2 points
HN discussionSubmitted Dark Side of Posix APIs as a story · 2 points
HN discussionSubmitted 40ms bug: a missing writev, Nagle's algorithm, and delayed ACKs as a story · 2 points
HN discussionSubmitted Throw Away Code as a story · 2 points
HN discussionSubmitted SIMD Library Plans as a story · 2 points
HN discussionSubmitted Atomics and Memory Ordering as a story · 2 points
HN discussionSubmitted More tricks up in the ArcSwap's sleeve as a story · 1 points
HN discussionSubmitted Tricks in Arc Swap (2019) as a story · 1 points
HN discussionSubmitted Using Const Generics in Slipstream as a story · 1 points
HN discussionSubmitted Saving Some Allocations as a story · 1 points
HN discussionSubmitted Dark side of Posix APIs: handling siginfo_t in Rust as a story · 1 points
HN discussionSubmitted Ms Bug as a story · 1 points
HN discussionSubmitted Performance Cheating as a story · 1 points
HN discussionSubmitted Hyper Traps as a story · 1 points
HN discussionSubmitted Runtime Configuration Reloading in Rust as a story · 1 points
HN discussion