Node.js diagnostics - howtos
Table of contents
| Get started |
|---|
| tbd: how to choose which tool to use |
| Guides |
| about llnode |
| about node-report |
| flame graphs |
| heap dumps |
| tracking (de)optimizations |
| wip: core dumps |
| tbd: native debuggers (gdb and lldb) |
| External links |
| read this to really understand how asynchronous code runs |
Goal
The purpose of this repo is to collect all the intricate bits of knowledge about diagnosing what happens to node applications' performance, memory and production runtime.
- short documents
- link only to resources that should stay up
- make recognizing what's outdated easy
- make it useful as notes for someone who knows it already but needs details to be able to teach others without preparation
- Why does it focus on tools for Linux?
- Because people tend not to run web applications in production on Mac.