https://github.com/naugtur/node-diagnostics-howtos

https://github.com/naugtur/node-diagnostics-howtos

Last synced: 4 months ago
JSON representation

• Host: GitHub
• URL: https://github.com/naugtur/node-diagnostics-howtos
• Owner: naugtur
• License: other
• Created: 2017-02-03T13:14:28.000Z (over 8 years ago)
• Default Branch: master
• Last Pushed: 2018-06-12T03:14:34.000Z (over 7 years ago)
• Last Synced: 2025-04-09T13:45:02.687Z (6 months ago)
• Size: 159 KB
• Stars: 23
• Watchers: 3
• Forks: 9
• Open Issues: 1
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

          
# Node.js diagnostics - howtos

## Table of contents

| Get started |

| --- |

| tbd: [how to choose which tool to use](tbd.md) |

|**Guides**|

| [about llnode](llnode.md) |

| [about node-report](node-report.md) |

| [flame graphs](flame-graphs.md) |

| [heap dumps](heap-dumps.md) |

| [tracking (de)optimizations](optimizations.md) |

| wip: [core dumps](core-dumps.md) |

| tbd: [native debuggers (gdb and lldb)](tbd.md) |

| **External links** |

| [read this to really understand how asynchronous code runs](https://nodejs.org/en/docs/guides/event-loop-timers-and-nexttick/) |

----

### 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.