Observing Node.js: Using Metrics to Improve your Application Performance
summary
Uses Prometheus and Grafana with a Docker Desktop demo repo and autocannon load tests to show concrete fixes: moving a builder to module top-level cuts a measured CPU jump from a 60% CPU spike to about 5%, caching a large JSON avoids repeated fetches that drive CPU and GC, and fixing unhandled promises stops a growing in-flight requests leak that pushes 99.9th-percentile latency up. Shows how to read process CPU, event-loop lag, heap, request rate and percentiles together to pinpoint root causes.
AI-written summary · about
chapters (6)
- 0:00Introduction to metrics
- 1:32Key performance metrics
- 4:00Analyzing performance data
- 7:15Case study: Code inefficiency
- 13:54Case study: Memory leaks
- 21:20Case study: Leaky promises
related talks
21mCan you tell me if your Node app is healthy?
01h 04mNode.js performance analytics and best practices
38mWelcome to Mordor! Hunting Performance Issues in Node.js.
20mMonitoring, And Visualizing your Node.JS server with Open Source tools
34mOptimizing Performance in Large-Scale React & Node.js Applications
25mNode js applications diagnostics under the hood
09mNodejs Runtime Performance Tips
13mMy Node.js process is on fire