Menu
It says on the Node.js about page:
Node exits the event loop when there are no more callbacks to perform.
Is there a way to find out which callbacks are keeping Node from exiting?
946
Once file I/O is complete, it will call the callback function while passing the callback function, the content of the file as a parameter. So there is no blocking or wait for File I/O. This makes Node. js highly scalable, as it can process a high number of requests without waiting for any function to return results.
The callback queues are queues that hold callback functions to asynchronous operations when they have been completed in the background. They work in a first-in-first-out (FIFO) manner. We'll look at different types of callback queues later in this article. Note that Node.
EventEmitter.defaultMaxListeners By default, a maximum of 10 listeners can be registered for any single event.
As long as the callback code is purely sync than no two functions can execute parallel.
You can use process._getActiveHandles() and process._getActiveRequests()
See this discussion in node.js mailing list.
update: there is a good package for this - https://github.com/mafintosh/why-is-node-running
194
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With
