[nigrosimone]

uNetworking#1325 on top of the benchmark workflow, to see what the CI says about a real change.

[github-actions]

Benchmark: 7d49d31 against c8d4ee1

Scenario	Base req/s	Head req/s	Head / base	Rounds	Noise	Busy	CPU per request
http/hello-world	115910	114763	0.991x (-0.9%)	0.98 to 0.99	±2.7%	100% / 100%	8.62 / 8.71 us (1.010x)
http/headers	96551	94921	0.986x (-1.4%)	0.98 to 0.99	±3.5%	100% / 100%	10.36 / 10.54 us (1.014x)
http/json-post-1kb	53351	52818	0.985x (-1.5%)	0.97 to 1.00	±5.3%	100% / 100%	18.76 / 18.94 us (1.016x)
http/cached	129466	128312	0.991x (-0.9%)	0.99 to 0.99	±2.8%	100% / 100%	7.72 / 7.79 us (1.009x)
ws/echo-20b	119060	121176	1.018x (+1.8%)	1.01 to 1.03	±1.1%	100% / 100%	8.39 / 8.25 us (0.982x)
ws/echo-4kb	103676	104278	1.003x (+0.3%)	0.99 to 1.01	±1.8%	100% / 100%	9.64 / 9.58 us (0.998x)

4 rounds of 3s per scenario, each round loading base, head and a second process of each one after the other, in an order that changes every round. "Head / base" is the median of the per-round ratios of req/s and "Rounds" their range. "Noise" is how far base/base and head/head, the same code on both sides, got from 1 in this same run: that is what the machine did, so a row is marked only when the median moved further than that, at least 2%, and every round moved the same way: 👀 slower, 🏆 faster. "Busy" is the cpu time of the server process over the round and "CPU per request" that time divided by the requests it answered, with the head/base ratio judged against its own same-code band and bold when it cleared it. When busy is well under 100% the load generator set the pace, the req/s are its and the cpu per request is the column to read. Only the ratios are comparable across runs, the absolute figures depend on the runner.

Node v26.9.0, AMD EPYC 7763 64-Core Processor, 4 cores (server on cpu 0, load on 2,3), wrk -t2 -c100.