Pushing WireGuard on macOS to 5 Gbit/s
Comments on “Pushing WireGuard on macOS to 5 Gbit/s”
Claim-checked. Scored by all three judges, and its checkable claims were compared with the sources it cites. How far stories are checked
Firezone says it raised its macOS WireGuard client from about 1 Gbit/s to over 5 Gbit/s. Its reading of Apple's XNU source is that UDP writes never return EWOULDBLOCK, so packets drop at the interface queue and TCP inside the tunnel slows needlessly. Connected sockets, ENOBUFS handling, batched sendmsg_x and coalescing up to three TCP segments restored backpressure and cut per-packet cost. The 5.87 Gbit/s upload and 5.76 download figures come from one pair of M1 Macs over Thunderbolt, and the XNU buffer behavior was not independently verified.
Why it ranked
No. 12 of 144 with a score of 0.67. The panel rated it highest on technical depth (0.95) and new information (0.93), lowest on audience breadth (0.54). Placed No. 12, No. 26 by score alone: the placement terms moved other stories past it.
- AI judgeJudge 2claude-haiku-5-5
- Detailed, well-substantiated engineering writeup on macOS WireGuard/TUN/UDP internals and performance fixes; technically deep and novel, but niche in audience and promotional undertone from VPN vendor.
- AI judgeJudge 3gpt-5.6-luna
- A deeply technical, well-supported engineering account of macOS/XNU networking, backpressure, batching, and packet coalescing, with reproducible performance measurements and concrete implementation lessons for VPN and networking practitioners.
Each judge wrote its line after answering the rubric, with the site and the author still hidden. Every answer behind this is in the table under Score.
Score
0.67total under rubric v2.3
- Significance0.55
- Reader interest0.82
- Audience breadth0.54
- Practical relevance0.72
- Substantiated0.86
- Technical depth0.95
- New information0.93
- Counts against: Promotional0.10
- Counts against: Overclaim0.21
Each judge’s answer per question (0–1), their mean and spread, and what the question adds to the score (weight × mean).
| Question | Judge 1 | Judge 2 | Judge 3 | Mean | Spread | Weight | Contribution (weight times mean) |
|---|---|---|---|---|---|---|---|
| SignificanceHow much does this change what people in tech know or can do? | 0.52 | 0.40 | 0.72 | 0.55 | 0.32 | +0.24 | +0.131 |
| Reader interestWould a well-informed senior engineer or tech founder want to read this today, and likely pass it on? | 0.75 | 0.80 | 0.90 | 0.82 | 0.15 | +0.26 | +0.212 |
| Audience breadthHow many people who build technology does it concern? | 0.53 | 0.50 | 0.58 | 0.54 | 0.08 | +0.13 | +0.070 |
| Practical relevanceHow useful is it to someone who builds software or tech products? | 0.73 | 0.60 | 0.82 | 0.72 | 0.22 | +0.22 | +0.158 |
| SubstantiatedHow well is it backed? Consider whether it is the primary source, and whether its main claims come with data, code, a demo, a reproducible method or citations. | 0.89 | 0.80 | 0.90 | 0.86 | 0.10 | +0.05 | +0.043 |
| Technical depthHow technically substantive is it? | 0.99 | 0.90 | 0.95 | 0.95 | 0.10 | +0.05 | +0.047 |
| New informationDoes it contain information absent from the stories covered in the last 7 days (list provided)? | 0.90 | 0.90 | 0.98 | 0.93 | 0.08 | +0.05 | +0.046 |
| PromotionalIs it mainly marketing with little substance (a press release, ad or sponsored post with no real information)? A launch post that carries real news is not promotional. | 0.06 | 0.15 | 0.08 | 0.10 | 0.09 | −0.19 | −0.018 |
| OverclaimDo the headline or conclusions claim more than the body supports? | 0.30 | 0.20 | 0.12 | 0.21 | 0.18 | −0.11 | −0.023 |
| Sum of contributions | +0.666 | ||||||
| Claim-check penalty | 0.000 | ||||||
| Total, as published | 0.666 | ||||||
Spread is the highest minus the lowest judge answer. marks a spread above 0.40: the judges disagree, and the story is marked contested.
The badge for this ranking, for the author's page or anyone's: one line of HTML, and it links back here.
<a href="https://rubric.hrih.si/editions/2026-11-19/12/"><img src="https://rubric.hrih.si/badge/2026-11-19/12.svg" alt="Ranked #12 on Rubric, 19 Nov 2026" width="245" height="28"></a>Claim check
Claim check: 2 no source given · 1 couldn’t check. Each claim is compared with the source the article itself cites; a flag is published only when both checkers agree.
No source givenNumber
Firezone optimized its macOS Client from around 1 Gbit/s to over 5 Gbit/s throughput.
The article gives no link or citation for it.
The article says “we optimized the Firezone macOS Client from around 1 Gbit/s to over 5 Gbit/s”
The source says No source to compare with.
No source givenBenchmark result
On the M1 Mac benchmark pair connected via Thunderbolt, Firezone achieves 5.87 Gbit/s upload and 5.76 Gbit/s download.
The article gives no link or citation for it.
The article says “On these M1 Macs, Firezone achieves 5.87 Gbit/s upload and 5.76 Gbit/s download”
The source says No source to compare with.
Couldn’t checkCausal conclusion
On XNU, UDP sockets effectively do not use their send buffer: packets go straight to the interface transmit queue and the buffer fill level stays at 0.
The source was unreachable, paywalled or too long, or the two checkers disagreed.
The article says “Instead of being buffered, the packet is handed directly to the network interface's transmit queue and the buffer's fill level always remains 01”
The source says No passage could be compared.
Source cited by the article: github.com/apple-oss-distributions/xnu/blob/xnu-12377.121.6/bsd/net/dlil.c
Also covered by
No other coverage was clustered with this story.
Elsewhere
Elsewhere: HN 19 pts, front page
Recorded for context only, checked 19 Nov 2026, 05:47 UTC. It played no part in the ranking.