All 15 Event Loop & Non-blocking IO questions
More in Event Loop & Non-blocking IO
What does it mean that Node.js's I/O is handled by libuv, and how does libuv abstract different operating systems' I/O mechanisms? What is the difference between synchronous and asynchronous versions of the same core Node.js API, using fs.readFile vs fs.readFileSync as an example, and when is the synchronous version actually appropriate? How would you measure how 'busy' the event loop is in a running Node.js process using a simple technique? What are the distinct phases of the Node.js event loop, and what kind of callbacks does each phase execute? What is the poll phase of the event loop, and under what specific conditions does it block waiting versus move on immediately? What is the difference between how Node.js handles I/O-bound concurrency versus CPU-bound work, and why does this distinction shape Node.js's ideal use cases? How would you use async_hooks (the lower-level predecessor to AsyncLocalStorage) to trace the lifecycle of asynchronous resources in Node.js? How does the V8 JavaScript engine's microtask queue interact with the Node.js event loop's macrotask phases, and why does this occasionally surprise developers?
Advertisement
Node.js › Event Loop & Non-blocking IO

What is 'event loop lag' (or 'event loop delay'), and how would you monitor it in a production Node.js application?

Advanced

Answer

Event loop lag measures the delay between when a scheduled callback (like a timer) should ideally fire and when it actually does, serving as a proxy for how 'busy' or blocked the event loop currently is -- rising lag indicates the event loop is spending too much time on synchronous work (or too many queued callbacks) to process new events promptly, directly translating into slower response times for every request being handled by that process, making it a critical production health metric.
const { monitorEventLoopDelay } = require('node:perf_hooks');

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

setInterval(() => {
  console.log('Mean lag (ms):', histogram.mean / 1e6);
  histogram.reset();
}, 10000);
Real-world example A team notices their API's response times degrade under load despite CPU usage looking reasonable, and adds event-loop-delay monitoring which reveals significant lag spikes correlating exactly with a specific synchronous data-transformation function, leading them to move that work to a worker thread.

Common follow-ups: How does event loop lag differ from and relate to overall CPU usage as a health metric?;What threshold of event loop lag typically indicates a genuine problem requiring intervention?

Debugging & Diagnostics;Performance Optimization & Profiling
All 15 Event Loop & Non-blocking IO questions