JavaScript

You're viewing a free preview. Sign in free to read every script.

Why this exists "The service is slow" and "the pod keeps getting OOMKilled" are the two most common Node.js production problems. Both are solved the same way as in any language: measure, do not guess . Node ships with…

Profiling Node.js: CPU Profiles, Finding a Memory Leak, Heap Limits and Heap Snapshots

Find out why a Node service is slow or growing: record a CPU profile with --cpu-prof and read it with a small script, watch a leaking cache hit the heap limit and exit with code 134, fix it with a bounded cache, understand heap versus external memory, and take a heap snapshot for DevTools.

← Code Quality Gates: ESLint, Prettier, Type Checks, Pre-commit Hooks and CI Enforcement Secure Node.js Basics: Path Traversal, Command Injection, Prototype Pollution, Secrets, SSRF and Dependencies →