Matteo Collina @nodeland.dev · Jun 15

A default set from May 2015 was just changed for the first time. One number. One constant. And it was quietly costing Node.js up to 26% of its throughput on the workloads you run every day: file reads, HTTP parsing, and stream chunking. streamyard.com/watch/9y9Q4G...

1 likes 1 replies

?

Replies

Matteo Collina · Jun 15

It was a sensible choice in 2015. Different hardware, different apps. Then a decade passed and the assumption stopped matching reality. The change shipped in Node.js 26.3.0.