How is Node.js inherently faster when it still relies on Threads internally?

by

There are actually a few different things being conflated here. But it starts with the meme that threads are just really hard. So if they’re hard, you are more likely, when using threads to 1) break due to bugs and 2) not use them as efficiently as possible. (2) is the one you’re asking about.

Think about one of the examples he gives, where a request comes in and you run some query, and then do something with the results of that. If you write it in a standard procedural way, the code might look like this:

result = query( "select smurfs from some_mushroom" );
// twiddle fingers
go_do_something_with_result( result );

If the request coming in caused you to create a new thread that ran the above code, you’ll have a thread sitting there, doing nothing at all while while query() is running. (Apache, according to Ryan, is using a single thread to satisfy the original request whereas nginx is outperforming it in the cases he’s talking about because it’s not.)

Now, if you were really clever, you would express the code above in a way where the environment could go off and do something else while you’re running the query:

query( statement: "select smurfs from some_mushroom", callback: go_do_something_with_result() );

This is basically what node.js is doing. You’re basically decorating — in a way that is convenient because of the language and environment, hence the points about closures — your code in such a way that the environment can be clever about what runs, and when. In that way, node.js isn’t new in the sense that it invented asynchronous I/O (not that anyone claimed anything like this), but it’s new in that the way it’s expressed is a little different.

Note: when I say that the environment can be clever about what runs and when, specifically what I mean is that the thread it used to start some I/O can now be used to handle some other request, or some computation that can be done in parallel, or start some other parallel I/O. (I’m not certain node is sophisticated enough to start more work for the same request, but you get the idea.)

More Related Contents:

  1. Is it bad practice to have a constructor function return a Promise?
  2. Coordinating parallel execution in node.js
  3. How do I completely uninstall Node.js, and reinstall from beginning (Mac OS X)
  4. Client on Node.js: Uncaught ReferenceError: require is not defined
  5. Error: request entity too large
  6. How to parse JSON using Node.js? [closed]
  7. Asynchronous exception handling with bluebird promises
  8. How to format a UTC date as a `YYYY-MM-DD hh:mm:ss` string using NodeJS?
  9. Using socket.io in Express 4 and express-generator’s /bin/www
  10. Calling a JSON API with Node.js
  11. What is the best way to limit concurrency when using ES6’s Promise.all()?
  12. getting how many people are in a chat room in socket.io [duplicate]
  13. How to convert CSV to JSON in Node.js
  14. TypeError: firebase.storage is not a function
  15. Reading Excel file using node.js
  16. Inserting and Querying Date with MongoDB and Nodejs
  17. Socket.io + PhoneGap
  18. Manipulating the local file system with browser-based JavaScript and Node
  19. How to get updated document back from the findOneAndUpdate method?
  20. How do I add an action to watson conversation response?
  21. Firebase – Get Random Child From Database Node
  22. Loop through asynchronous request
  23. Error: 10 ABORTED: Too much contention on these documents. Please try again
  24. How to mock Axios with Jest?
  25. Does every object in JS have a toString() method?
  26. Promise.all().then() resolve?
  27. Is there a limit on the size of a string in JSON with Node.js?
  28. Where argument of first next() call goes? [duplicate]
  29. How to convert a string to ObjectId in nodejs mongodb native driver?
  30. How to run my node.js project on android?

Leave a Comment