It can't be true that in this basic test core is way faster than nodejs.Off course this is not the only metric used to measure performance between these two web technologies, but I am wondering what am I doing wrong in the side? Being a professional developer and wishing to adapt in personal projects, this is kind of putting me off - as I'm a little paranoid about performance.I thought is faster than core (in general - as seen in various other benchmarks) I just want to prove it to myself (to encourage myself in adapting node.js).Please reply in comment if you want me to include more code snippets. NET Core app Server response "I always thought is faster than core" - I'm curious why you think that?
Both of them are running in production mode and without a logger attached to them. Here is the action method that render this page Can't believe my eyes!I've not seen any benchmarks that would support this (the main reasons I've heard for adopting were "ease of use" and "faster development/iteration time")@Unholy Sheep It's all what I heard mate, I also heard it's "easy to use" and "faster to develop" too, generally from people use never worked in ASP. I'm not bragging about any technology - but this is the pattern I [email protected] using cluster module Node Js spawns multiple workers doing and share the load of main process which is listening on single process.It just avoids having to set up multiple application on different ports.For these IO-bound workloads, the move to avoid blocking the processing threads was that dramatic.Now let's bring it to today, where that influence has rippled through the industry and allow dotnet to take advantage of its improvements.