Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 2
    the diagram given in that blog post seems to be wrong, what they have mentioned in that article is not completely correct. Commented Feb 9, 2020 at 8:50
  • 3
    AFAIK, there's no blocking I/O in node (unless you use sync APIs), the thread pool is only used momentarily to handle I/O responses and deliver them to the main thread. But, while waiting the I/O request [there's no thread]( blog.stephencleary.com/2013/11/there-is-no-thread.html) , otherwise the thread pool would get clogged pretty quickly. Commented Feb 13, 2021 at 2:21
  • i cleared the confusion stackoverflow.com/a/70161215/4034825 Commented Nov 30, 2021 at 5:19
  • I think the last three steps are only true for non blocking i/o. It doesnt check thread pool for threads when you have blockcing or sync task. Commented Dec 17, 2022 at 15:35