Welcome to Mordor! Hunting Performance Issues in Node.js.
summary
Shows concrete diagnostics: use V8 metrics (process.memoryUsage, heap snapshots via v8-profiler) and load them into Chrome devtools to spot leaks caused by closure cycles that make GC bail out; run CPU profiling and visualize with D3 sunburst to find hotspots — discover Express defaulting to development doubles latency by recompiling Jade, and a Netflix case where auto-added routes append into an O(n) routing table. Recommends Node Monitor, NSolid, Ruxit, AppDynamics/New Relic and async_hooks / tracing work for end-to-end traces.
AI-written summary · about
chapters (8)
- 0:00Start
- 7:24Memory Management
- 8:04Process Memory Usage
- 8:58Garbage Collection
- 10:23Memory Leak
- 18:26Cpu Profiling
- 25:17Node Monitor
- 36:32Takeaways
related talks
39mWelcome to Mordor! Hunting Performance Issues in Node js
01h 04mNode.js performance analytics and best practices
43mFinding memory leaks and CPU bottlenecks with Node.js debug tools
50mDebugging Node.js in Production
22mExamining Observability in Node.js
25mNode js applications diagnostics under the hood
09mNodejs Runtime Performance Tips
57mTroubleshooting Node.js Applications Under the Hood