René's URL Explorer Experiment

Title: http: reduce per-request allocations in the server by mcollina · Pull Request #65802 · nodejs/node · GitHub

Open Graph Title: http: reduce per-request allocations in the server by mcollina · Pull Request #65802 · nodejs/node

X Title: http: reduce per-request allocations in the server by mcollina · Pull Request #65802 · nodejs/node

Description: Removes allocations and repeated work the HTTP server performs for every request: Per-request bound functions: updateOutgoingData.bind() becomes one closure per connection reused by every response, and the per-request resOnFinish.bind() becomes a shared 'finish' listener that reaches everything through the connection state stored on the response. req.headers materialization: the requireHostHeader check (req.headers.host), the Expect check, and optimizeEmptyRequests' body-header check now scan rawHeaders (over the same range the headers getter exposes) instead of building the whole headers object — with a toLowerCase() per header name — for every request even when the application never reads req.headers. ServerResponse options object: cached per server; custom response classes keep receiving a fresh object since they may retain or mutate it. Status line: cached per status code when the reason phrase is the default (also skipping its character validation, which cannot fail for the built-in phrases). Date: header line: the complete line is cached alongside the existing one-second utcDate() cache. Keep-alive header pair: Connection: keep-alive\r\nKeep-Alive: timeout=N is rendered once per server settings instead of per response. Lenient-validation lookup: the 4-level option chain is computed once per message. Responses are byte-identical to main (verified by diffing raw responses). Benchmarks (i7-7700, server pinned to one core, wrk -t2 -c50 on separate physical cores, interleaved rounds, CPU from /proc//stat): workload main this PR Δ hello world, 1 request header 26.0 µs/req 24.2 µs/req −6.9% CPU, +7.5% req/s (8/8 rounds) hello world, 8 request headers 28.7 µs/req 25.3 µs/req −11.8% CPU, +13% req/s (5/5 rounds) Sampled heap allocation drops from 5206 to 4531 B/request (−13%); the req.headers build (~200 B + per-name toLowerCase per request) disappears from the profile entirely. test/parallel/test-http-*, test-http2-*, test-stream-*, test-net-*, test-https-* and the http diagnostics-channel suites all pass (1171 tests). Follow-up to #65732 and #65749. 🤖 Generated with Claude Code https://claude.ai/code/session_01TV8WVjiHJPR2hW4D6h1Xpr

Open Graph Description: Removes allocations and repeated work the HTTP server performs for every request: Per-request bound functions: updateOutgoingData.bind() becomes one closure per connection reused by every response...

X Description: Removes allocations and repeated work the HTTP server performs for every request: Per-request bound functions: updateOutgoingData.bind() becomes one closure per connection reused by every response...

Opengraph URL: https://github.com/nodejs/node/pull/65802

X: @github

direct link

Domain: github.com

Links:

Viewport: width=device-width