Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

.NET and Node.JS – Performance Comparison

salmanq.com

Post reply on HN
Print view View original

71–80 of 119 posts

Re: .NET and Node.JS – Performance Comparison

#71

Post by base698 »

meryn wrote: post #48

I posted this comment: "It's obvious that you're new to Node.js. First of all, you should be aware that Async.js is a mere flow-control library. It does not offload work to separate threads, and neither is it able to parallelize work. Internally, it mostly does bean-counting (but very helpfully so). As you can see in the source https://github.com/caolan/async/blob/master/lib/async.js#L35... async.sortBy simply uses A…

Good break down of .NET Array.sort

It's kind of funny he talks about it being fast for due to non-blocking IO:

One of the key reasons most argue is that node.js is fast, scalable because of forced non-blocking IO, and it’s efficient use of a single threaded model.

...then goes on and sets up a benchmark which is more dependent on CPU than IO. Not to mention as mentioned here that benchmark itself is flawed.

In my experience Node is faster in the case of most web apps that select a row from the db, read network requests to do aggregation, or update a column in a db. Anything that does do CPU computation generally uses a native hook or a different tech altogether.

Re: .NET and Node.JS – Performance Comparison

#73

Post by meryn »

niggler wrote: post #65
meryn wrote: post #48

I posted this comment: "It's obvious that you're new to Node.js. First of all, you should be aware that Async.js is a mere flow-control library. It does not offload work to separate threads, and neither is it able to parallelize work. Internally, it mostly does bean-counting (but very helpfully so). As you can see in the source https://github.com/caolan/async/blob/master/lib/async.js#L35... async.sortBy simply uses A…

meryn this is an opportunity for you to properly design a benchmark and write your own blog post. EDIT: I meant to imply that most people who write benchmarks usually aren't experts in every language/framework in the comparison, so it would be nice to see someone who is competent in both .NET and in nodejs put together a benchmark.

I'll take that as a compliment. ;)

If I ever would be doing such a thing, it would be more of a lesson in how to use node.js properly (even for non-typical tasks like sorting) then a performance comparison between node.js and .Net. Even then, I don't think it would be very interesting for people who like to read about node.js. It would be non-news to them, and for an atypical use-case.

I actually have no interest at all in getting a .net stack running on my mac.

The misleading information is what bothers me, so I hope to see it corrected. It's especially harmful because his blog will be most likely read by people who naturally favor .net. It's not even a tech blog per se. Then objective information is all the more important. (EDIT: Actually it does seem to a tech blog, which surprises me a bit, given the superficiality of his analysis)

You can see at the end of his posts, how he diverts from the main subject and goes on about (I'm sure to be) wonderful technologies and possibilities that the .net stack offers.

Re: .NET and Node.JS – Performance Comparison

#75

Post by niggler »

meryn wrote: post #73
niggler wrote: post #65

Earlier quoted context omitted.

meryn this is an opportunity for you to properly design a benchmark and write your own blog post. EDIT: I meant to imply that most people who write benchmarks usually aren't experts in every language/framework in the comparison, so it would be nice to see someone who is competent in both .NET and in nodejs put together a benchmark.

I'll take that as a compliment. ;) If I ever would be doing such a thing, it would be more of a lesson in how to use node.js properly (even for non-typical tasks like sorting) then a performance comparison between node.js and .Net. Even then, I don't think it would be very interesting for people who like to read about node.js. It would be non-news to them, and for an atypical use-case. I actually have no interest at…

"I actually have no interest at all in getting a .net stack running on my mac."

How does nodejs performance on windows compare to to OSX or linux?

Re: .NET and Node.JS – Performance Comparison

#77

Post by pilif »

It's funny how everybody posts their theories of why the benchmark is wrong (or done by the wrong person) and nobody actually tries out the code they think is better. So instead of guessing, let's implement that corrected version of the node.js application and run the benchmark again.

In my case, I admit, I don't have Windows ready to reproduce the result, but then I'm also not complaining about how the test was done, nor do I care about this at the current point.

If I ever have issues with performance of an application, then I will be doing the profiling and evaluating other options. I certainly wouldn't use some benchmark I'm too lazy to reproduce as a basis for selecting the technology to use. Instead, I use the tool I'm most comfortable with, I see the most advantages from or I just like best.

While the OP's benchmark might have been (and IMHO probably was) flawed, at least they provided source code and documentation for us to improve and re-run it. That's way more important than to know who they are and what their motivations might be.

Re: .NET and Node.JS – Performance Comparison

#78

Post by addlepate »

antihero wrote: post #34

Until Mono becomes 100% supportable, none of the advantages of .NET outweigh the misery of having to use Windows for development and serving.

I agree, unfortunately. I have seen code written to work around bugs in Mono and I just can't subject myself to that, personally. It seems crazy-making. And the Windows stack is just yuck, of course.

Re: .NET and Node.JS – Performance Comparison

#79

Post by meryn »

pilif wrote: post #77

It's funny how everybody posts their theories of why the benchmark is wrong (or done by the wrong person) and nobody actually tries out the code they think is better. So instead of guessing, let's implement that corrected version of the node.js application and run the benchmark again. In my case, I admit, I don't have Windows ready to reproduce the result, but then I'm also not complaining about how the test was done…

"let's implement that corrected version of the node.js application and run the benchmark again." - Do it. I'm curious. :)
Post reply on HN