| 1 | - There may be long-running asynchronous activities
|
| 2 | - This can mean that the bottleneck is not the Node process at all, but rather an I/O operation
|
| 3 | - Diagnose: Use `clinic bubbleprof` to explore asynchronous delays – run <code class='snippet'>clinic bubbleprof -h</code> to get started.
|