Nodejs Runtime Performance Tips
summary
A concrete checklist of what changes performance and how to measure it: a microbenchmark shows one implementation taking 40 ms vs 7 ms because repeated pushes trigger garbage collection, Node runs with --inspect and Chrome DevTools profiler to record CPU and memory, the memory profiler shows 100 allocations per second as blue bars tied to a retained array, and simply clearing that array turns blue bars to gray and removes the leak, proving the fix.
AI-written summary · about
chapters (3)
related talks
01h 04mNode.js performance analytics and best practices
38mWelcome to Mordor! Hunting Performance Issues in Node.js.
39mWelcome to Mordor! Hunting Performance Issues in Node js
38mUnderstanding Memory Behavior on Nodejs
34mUnderstanding JavaScript Performance
43mFinding memory leaks and CPU bottlenecks with Node.js debug tools
46mHow much performance can you get out of JavaScript?
30mMemory Don't Forget To Take Out The Garbage