How Fixing a Bug in NodeJS Accidentally Doubled Performance

on YouTube ↗26m

" summary

A Node.js HTTP keep-alive bug is identified that leaves sockets and memory hanging under browser-like traffic. The talk presents a 12-line core patch adding a keep-alive lifetime timeout (default ~5s) to reclaim idle sockets after response end, and shows benchmarks and large-scale simulated-client tests demonstrating reduced heap pressure and over 2× faster socket teardown, plus notes on test coverage and compatibility caveats.

AI-written summary · about

" chapters (8)

1. 0:00Introduction
2. 3:33Node.js socket leak
3. 8:21Patch development
4. 11:59Fix details
5. 16:48Patch use
6. 19:15Further research
7. 21:31Open source contributions
8. 23:02Performance boost

" related talks

• 26mCan we Double the Node.js HTTP Client Throughput?Matteo Collina · OpenJS World 2021
• 22mThe Journey About How I Fixed a Bug in the Node.js Core That Affected Thousands of PackagesErick Wendel · JSConf Korea 2022
• 01h 04mNode.js performance analytics and best practicesSebastian Springer · International JavaScript Conference Munich 2019
• 30mNode.js Deep DebuggingGireesh Punathil · OpenJS World 2021
• 09mNodejs Runtime Performance TipsYonatan Kra · Node Congress 2021
• 23mThe Journey About How I Fixed a Bug in the Node.js Core that Affected Thousands of P...Erick Wendel · OpenJS World 2022
• 34mEvent loop tales on I/O bound Node.js applicationsAlessandro Aglietti · NodeJS Italian Conference 2018
• 53mMastering Node.js PerformanceTamar Twena-Stern · iJS 2018 Spring