While your cluster example does the job quickly, it exits the process early (right after reading is…
Abdullah Ali
1

I agree with the analogy but the problem is that most of the time it will be the I/O operations that will take time and when using a thread model you will spend a lot of cpu and memory for spawning new threads while waiting for all that I/O. Node solves that very well by not spending any resources while waiting for I/O.

If you are choosing JavaScript for a video encoding problem you haven’t done your homework- it is not a silver bullet. however — node is great for handling json and queuing jobs etc, for that cluster and a queue is perfect way to use the whole hardware.

I will check my timings with your code.

One clap, two clap, three clap, forty?

By clapping more or less, you can signal to us which stories really stand out.