Debugging Node.js in Production
summary
Shows how to find CPU hotspots by sampling with perf and turning JIT addresses into JavaScript stacks via --perf-basic-prof, visualizing with 0x/FlameGraphs to spot sync crypto and template hashing that block the event loop; demonstrates postmortem debugging by enabling --abort-on-uncaught-exception, setting ulimit and loading core files into MTP/autopsy to inspect V8 frames; proves heap-diffing with heapdump + Chrome DevTools to find leaked incoming request objects and fixes by handling close vs end and switching to async hashing.
AI-written summary · about
chapters (19)
- 0:00Start
- 3:08Why Is It Important To Be Able To Debug Note in Production as Opposed to Your Development or Staging
- 4:04Cpu Intensive Code
- 5:12Garbage Collection
- 7:38Cpu Sampling
- 11:02Stack Traces
- 17:24Generate a Frame Graph
- 22:13Recap
- 23:47Bonus Tip Number Two
- 24:36Post-Mortem Debugging
- 25:17Reproducibility
- 25:47Core Dump
- 36:34Stack Trace
- 39:44Memory Leaks
- 40:07Memory Leak
- 41:21Demo
- 41:50Heap Dump
- 46:28Recap Slides
- 47:57Debugging Memory Leaks
related talks
25mNode js applications diagnostics under the hood
57mTroubleshooting Node.js Applications Under the Hood
43mFinding memory leaks and CPU bottlenecks with Node.js debug tools
39mWelcome to Mordor! Hunting Performance Issues in Node js
28mPost mortem NodeJS debugging
38mWelcome to Mordor! Hunting Performance Issues in Node.js.
50mPost-Mortem Debugging in Node.js
01h 04mNode.js performance analytics and best practices