Practise the standard verbs for diagnosing and fixing Node.js event loop blocking.
0 / 5 completed
1 / 5
Fill in: 'We ___ heavy synchronous work off the main thread into a worker so it never blocks other requests being handled.'
We 'move' work — the standard, simple collocation for relocating a task to another execution context. The other options are less idiomatic here.
2 / 5
Fill in: 'A large synchronous JSON.parse on every request can ___ the event loop stalled long enough to trip health checks.'
We say synchronous parsing will 'leave' the loop stalled — the standard, natural collocation here. The other options aren't idiomatic here.
3 / 5
Fill in: 'We ___ event loop lag continuously in production so a creeping regression gets caught before users start timing out.'
We 'monitor' lag — the standard collocation for ongoing observation of a metric. The other options aren't idiomatic here.
4 / 5
Fill in: 'We ___ a CPU-bound task into smaller chunks with setImmediate so it yields back to the loop between steps.'
We 'split a task' — the standard, established collocation for dividing blocking work into cooperative steps. The other options aren't the recognised term here.
5 / 5
Fill in: 'We ___ a profiler under load to pinpoint exactly which function is hogging the event loop the longest.'
We 'run a profiler' — the standard, simple collocation for executing a diagnostic tool. The other options are less idiomatic here.