Here's a question to you: On what kind of hardware, which Node.JS version, what operating system, callback of which function... ?
Also always remember: These kind of benchmarks are usually nice to look at, but do never reflect real-life. Node.JS is fast. How fast depends on a lot of factors. But at the end of the day, it really boils down to how you write your application. If you do not optimize your code, it doesn't even matter which language, compiler or VM you use or how fast it was advertised as; it will always be slow.
So instead of searching some benchmark on Google for you, here is my advice: Write your application. Is it too slow? Find the hot path and analyse bottle necks. Improve the code. Is it still too slow? Have you tried using multiple processes (cluster module)? Use it (you might like the pm2 library)! Still not fast enough? Optimize further. Maybe write a C-module for Node.JS for your computations (JS is really bad with computations; that's something to take into consideration before you choose Node.JS). Still not fast enough? Then you are not using enough computation power and you need more performant hardware or just more hardware in general. All these steps are the same for any application and any language. If you think Node.JS is a good choice (after researching it and all possible alternatives), you should go for it and make the best out of it.
Marco Alka
Software Engineer, Technical Consultant & Mentor
Here's a question to you: On what kind of hardware, which Node.JS version, what operating system, callback of which function... ?
Also always remember: These kind of benchmarks are usually nice to look at, but do never reflect real-life. Node.JS is fast. How fast depends on a lot of factors. But at the end of the day, it really boils down to how you write your application. If you do not optimize your code, it doesn't even matter which language, compiler or VM you use or how fast it was advertised as; it will always be slow.
So instead of searching some benchmark on Google for you, here is my advice: Write your application. Is it too slow? Find the hot path and analyse bottle necks. Improve the code. Is it still too slow? Have you tried using multiple processes (
clustermodule)? Use it (you might like thepm2library)! Still not fast enough? Optimize further. Maybe write a C-module for Node.JS for your computations (JS is really bad with computations; that's something to take into consideration before you choose Node.JS). Still not fast enough? Then you are not using enough computation power and you need more performant hardware or just more hardware in general. All these steps are the same for any application and any language. If you think Node.JS is a good choice (after researching it and all possible alternatives), you should go for it and make the best out of it.