.NET and Node.JS – Performance Comparison
salmanq.com
.NET and Node.JS – Performance Comparison
1–10 of 119 posts
Re: .NET and Node.JS – Performance Comparison
#2Re: .NET and Node.JS – Performance Comparison
#3.net is faster than node but you absolutely failed at showing it.
Re: .NET and Node.JS – Performance Comparison
#4> I work for Microsoft as a software engineer for Bing in Silicon Valley. My group specializes in building platform and experiences for consumers. ( http://www.salmanq.com/ )
Re: .NET and Node.JS – Performance Comparison
#5Re: .NET and Node.JS – Performance Comparison
#6This is terrible. You are benchmarking node.js on exactly the thing everyone knows it is terrible at. Besides that yiur scenario is completely unrealistic and your google efforts Should have tipped you off. There are no results for sorting algorithms on node because nobody sorts on node.js. This is CS102.. Why would anyone ever sort more than 50 items on the server side of a web application. .net is faster than node…
Now granted every tool has its strengths and weaknesses this benchmark shows a very large difference in operations that aren't uncommon in web servers.
Sorting in memory should concern you, since caching happens in the memory. Again, I don't know the state of ORM technology in nodejs but any NHibernate user will be able to tell you that level 2 caches are a common thing and they will boost the benchmarks even further if you were to compare it to a nodejs stack.
The only scenario where I see nodejs faster and better than .NET are the very smallish script scenarios like a log receiver etc, where no state is needed and minimal memory footprint is required
Re: .NET and Node.JS – Performance Comparison
#7(keep in mind, microsoft haters, that microsoft is currently a HUGE proponent of node.js - a lot of the Azure Mobile Services and the like are built on node)
Re: .NET and Node.JS – Performance Comparison
#8Re: .NET and Node.JS – Performance Comparison
#9mind blown
Re: .NET and Node.JS – Performance Comparison
#10However, I would guess that typical Node.js apps would be better at handling concurrent connections than typical Asp.Net apps; since Asp.Net apps are not usually written in non-blocking style.