Dev.to1 min read
Detecting Event Loop Blocking in Production...
You're on call. Alerts fire. Your Node.js service is responding slowly — or not at all. You suspect event loop blocking, but the app is running in production. You can't redeploy with --inspect. You can't add require('blocked-at') to the source. You definitely can't restart it. What do you do? This is the problem that led me to build node-loop-detective — a diagnostic tool that attaches to a running Node.js process, detects event loop blocking and lag, and tells you exactly which function in whic
Read original on dev.to0
0Related
Hacker News
$500 GPU outperforms Claude Sonnet on coding benchmarks
Discussed on Hacker News with 377 points and 217 comments.
377
217Hacker News
Whistler: Live eBPF Programming from the Common Lisp REPL
Discussed on Hacker News with 115 points and 13 comments.
115
13Hacker News
Anthropic Subprocessor Changes
Discussed on Hacker News with 98 points and 44 comments.
98
44Get the 10 best reads every Sunday
Curated by AI, voted by readers. Free forever.
Liked this? Start your own feed.
Comment
Sign in to join the discussion.
Loading comments…