Many developers wonder at some point in their Node.js programming journey that, is Node.js really single-threaded? If it is, how is it able to do a...
For further actions, you may consider blocking this person and/or reporting abuse
I will do a joke. It will be very bad.
So Node.js is married-threaded.
It's been 6 hours. How to get this out of my head? It's very bad. 😣
Very bad indeed
I concur
So does this mean that there's no advantage in running Node on a super beefy 16 core machine?
Honestly, if you're looking to make use of heavy multithreading; Javascript just isn't the language you should be looking at I'm fraid
It's a practice to spawn multiple instances of the app with this type of setup.
Have a look at cluster module.
nodejs.org/api/cluster.html
To get started with multiple instances, have a look at pm2. You can spawn as many instances as your cpu cores.
pm2.keymetrics.io/
More an aside, but this was a great Node.js course on Frontend Masters that I did once. It touches on the usage of
libuvunder the hood for anyone who finds this discussion topic fascinating frontendmasters.com/courses/server...From what I can tell (correct me if I'm wrong), this uses service workers under the hood.
Those have the problem that you're not able to share memory, so if you want to pass large amounts of data around, you're effectively copying it every time it moves between threads.
While perhaps not problematic for some, I see this cause problems on large scale if you're not careful about what you're passing around; as well as the issue that suddenly you're not passing by reference whereas a regular function call would (for objects etc).
Asynchronous execution does not mean parallel execution. Node runs asynchronous tasks concurrently.
True to some extent(per each worker). But, offloading multiple tasks to libuv thread pool essentially make it parallel.