Node.js: Hot-Path Performance Push

The biggest signal is a coordinated cut to per-call overhead across require, native callbacks, HTTP validation, web streams and SQLite. Reliability fixes for large buffers and HTTP/2 resets round out the day.

Duration: PT2M43S

Episode overview

This episode is a short developer briefing from Node.js.

It explains recent repository work in plain language.

  • Show: Node.js
  • Published: 2026-09-29T13:09:04Z
  • Audio duration: PT2M43S

Transcript excerpt

This excerpt keeps the crawler page concise. Listen to the episode or use the RSS feed for the full update.

Good morning, it's September 29th, 2026.

The headline is performance. Across streams, database, module loading, native callbacks and HTTP, the work is all about removing tiny per-call costs that add up under load.

First, hot-path allocations. Merged change 63884 splits the require cache into two levels so cached requires do two allocation-free lookups instead of building a fresh cache key string every time. That string build and garbage collection churn was described as the largest per-call cost on cache hits. In native code,…

Second, shared shapes for repeated objects. Proposal 66392, round 20 of web streams performance work, moves for-await iterator methods onto a shared prototype instead of rebuilding them from an object literal on every call, targeting short-lived streams like a response body read once per request. In parallel,…

On reliability, 66325 corrects buffer index of returning a negative position for matches beyond 2 gigabytes, caused by a signed 32-bit conversion. And 66314 reorders HTTP2 shutdown to submit reset before emitting aborted, so a listener that destroys the stream no longer prevents the reset from reaching the peer.…

Watch for whether the streams, SQLite and…

Nearby episodes from Node.js

  1. Speed Gains and Native Crash Fixes
  2. Weekly Recap - Speed on Hot Paths, Tighter Boundaries, Cleaner APIs
  3. Hot-Path Speedups and a Major Permission Change
  4. HTTP Hot Path Speedup and SQLite Rename
  5. Speed Push, Memory Cuts and Crash Fixes
  6. HTTP Speedups and Runtime Hardening
  7. Crypto Correctness Sweep, Faster Web Streams, VFS Maturity
  8. SQLite Virtual Tables and Speed Push