The benchmark should has a new try further, when Asm.js will be added to V8. Sorting arrays of numbers could have another speed.
.NET and Node.JS – Performance Comparison
81–90 of 119 posts
Re: .NET and Node.JS – Performance Comparison
#82It'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…
Still, there is nothing that annoys me more than when someone who is well versed in one toolset, and new to another toolset has the audacity to conduct a comparison and pretend like they did it correctly.
I'm glad he provided source code, but he clearly doesn't know Node well enough to provide an Apples to Apples comparison. Maybe .NET will blow Node away? Fine, but make sure you know Node well before you do the test.
Still, it's a nice conversation to start. I don't care how much I hate the company that builds it: if a tool is best for a job I want to know about it.
But your complaint that nobody is doing the tests: C'mon, how many Node experts even have Windows laying around?
Re: .NET and Node.JS – Performance Comparison
#83The author notes about himself: > 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/ )
I just want to point out (as a Microsoft employee) that Microsoft is very actively using node.js internally. Many services are already using it and many more are starting projects with it. I suspect the author did this as an evaluation to see which would work best for a future project, not a teardown piece on the platform. We really love node.js - seriously!
My friend works now for Skype/rosoft and they hired him particularly because of his knowledge of Node.js and JavaScript.
Re: .NET and Node.JS – Performance Comparison
#84I 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 exp…
"...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."
Thank you. It amazes me how some people can write code in a framework like Node without even understanding the event-driven paradigm's strength and weaknesses. I was sitting there reading it, and then he states he is using a file sort??? WTF? As if anyone would use Node for that purpose.
Re: .NET and Node.JS – Performance Comparison
#85It'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…
Still, there is nothing that annoys me more than when someone who is well versed in one toolset, and new to another toolset has the audacity to conduct a comparison and pretend like they did it correctly. I'm glad he provided source code, but he clearly doesn't know Node well enough to provide an Apples to Apples comparison. Maybe .NET will blow Node away? Fine, but make sure you know Node well before you do the test…
Try it on mono?
Re: .NET and Node.JS – Performance Comparison
#86Until Mono becomes 100% supportable, none of the advantages of .NET outweigh the misery of having to use Windows for development and serving.
Um. Mono supports just about everything these days: http://www.mono-project.com/Compatibility
There is a reason why people are using it to simultaneously develop for Win, OSX, Linux, Android, iOS, XBOX, Wii, etc....
Re: .NET and Node.JS – Performance Comparison
#87It'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. :)
I'm not sure it would be worth it. While I think it is neat to finally see .NET popping up more I really don't see what this benchmark proves even if the C# and js both sorted the same type of data (string/floating point).
Re: .NET and Node.JS – Performance Comparison
#88Until Mono becomes 100% supportable, none of the advantages of .NET outweigh the misery of having to use Windows for development and serving.
Its not only that. For me, Visual Studio, the best single piece of software ever made, should be made available too - which unfortunately probably ain't gonna happen. It just saves so much time and makes the process such a breeze, that it was what converted me to windows to begin with...
Visual Studio is the greatest set of training wheels ever made. Beautiful, shiny training wheels that let you coast along and drink and eat without worrying about falling over. The people using the training wheels just don't understand why the big kids flying by on only two wheels would ever do such a thing. It's so much harder! I don't want to make my life harder. I have code completion and fantastic syntax, error detection etc. Why would I give that up and make my life harder? But when you give it up, you soon start to learn to find the errors yourself.... your memory picks up again. Think about how many phone numbers you knew before you stored them all in a cell phone. Think about how many you know now....
Every tool user will think tools more complicated than there's are ridiculous. Visual Studio users will think Sublime Text users are morons who are making their lives harder for no reason. Sublime Text users will think this about Vim users...... but my analogy:
Visual Studio: training wheels Sublime Text: fat tire 5 speed bike Vim/Emacs: 21 speed skinny tire Tour de France bike
Re: .NET and Node.JS – Performance Comparison
#89If you do research and analysis NOT to find out the answer to a question but rather to JUSTIFY the answer you have decided (without evidence) is correct then the value of the results is nil.
Re: .NET and Node.JS – Performance Comparison
#90The author notes about himself: > 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/ )
Unless you can point to something incorrect or unfairly biased in that article - why does this matter?
While others have pointed out the issues, it is a critical observation to make because it often goes with a very strong selection bias. When someone wants to write that A is better than B -- which would be the obvious motivation of a Microsoft employee -- they will iterate through the cases until they can find evidence that they think supports that conclusion, then publishing that alone. In this case a rather terrible benchmark that, as so many others have mentioned, is really a sort comparison (against an incorrectly done node js sort, making it even worse).
I love .NET. I also love nodejs. The truth is that node is best as a glue system between technologies, and it works perfectly there.