Node.js Event Loop Lag Profiling: Diagnosing CPU Starvation and Microtask Blocking

Understanding Event Loop Saturation

Because Node.js executes JavaScript on a single thread, any synchronous operation—such as intensive JSON serialization, cryptographic hashing, or large array mapping—blocks the event loop. Inbound HTTP connections queue up in the OS socket buffer, leading to severe latency spikes and gateway timeouts.

Measuring Loop Lag with perf_hooks

import { monitorEventLoopDelay } from 'perf_hooks';

const histogram = monitorEventLoopDelay({ resolution: 20 });
histogram.enable();

setInterval(() => {
    console.log(`Event loop mean lag: ${(histogram.mean / 1e6).toFixed(2)} ms`);
    console.log(`Event loop p99 lag: ${(histogram.percentile(99) / 1e6).toFixed(2)} ms`);
    histogram.reset();
}, 5000);

If p99 exceeds 50ms, offload heavy compute tasks to worker threads or background queue processors.