Submission timeline
2007–2026One slot for every year since HN launched. Height is that year's peak points; orange marks a 100+ point or 50+ comment breakout. Select a bar to open its strongest thread.
First comments on top threads
HN comment orderA random thing I ran into with the defaults (Ubuntu Linux): - net.ipv4.tcp_rmem ~ 6MB - net.core.rmem_max ~ 1MB So.. the tcp_rmem value overrides by default, meaning that the TCP receive window for a vanilla TCP socket actually goes up to 6MB if needed (in reality - 3MB because of the halving, but let's ignore that for now since it's a constant). But if I "setsockopt SO_RCVBUF" in a user-space application, I'm actually capped at a maximum 1MB, even though…
Nice post. Some more references: 1. AWS re:invent talk on Network Performance: https://youtu.be/LjeXZItav34 2. Twitter thread on network optimization by colmmacc, Principal at AWS Network and Edge Engineering orgs: https://threadreaderapp.com/thread/1099086415671877633.html 3. drewg123 on Jim Roskind's QUIC vs TCP: https://news.ycombinator.com/item?id=19461777 4. Google's BBR congestion algorithm for TCP and QUIC: https://ai.google/research/pubs/pub45646 5. The sophisticated HFSC (hierarchical fair service curve)…
Great content about linux network however not 100% accurate but fair enough for learning
This is a great summary, thank you. Also attribution for things like (https://blog.packagecloud.io/eng/2016/10/11/monitoring-tunin...) is very much appreciated.
The first top-level comment from each of the four biggest threads, in HN’s own order. Excerpts are shortened; open a comment for full context.
- Breakout years
- 2
- Total points
- 793
- Total comments
- 118
100+ points or 50+ comments
reference only — not used in Hall rules or ranking
reference only — not used in Hall rules or ranking