> From the questions we received around the specifics of our performance improvements, there seems to be two schools of thought: > 1. Of course it’s faster, Node is slow > 2. You must be doing Node wrong, it can be fast Allow me to offer a third :) When you rewrite something, it had better be faster! You know a lot more about how it works and how it's used than you knew at the outset. There was a recent post, about g…
Hey! Where could I find this post?
How Raygun increased throughput 20x with .NET Core over Node.js
51–60 of 61 posts
Re: How Raygun increased throughput 20x with .NET Core over Node.js
#52Earlier quoted context omitted.
It's not 30 times faster. Also, it doesn't matter which one is faster unless there is. Huge speed improvement. Your web server is not the bottleneck.
"Your web server is not the bottleneck." - Highly depends on your setup. But removing any 3rd party libraries, and external requests. Generally .NET core is faster.
Honestly, add another machine and the problem is solved. youll be able to afford a team of programmers to rewrite your app in any language of your choosing by the time you feel the slow down.
I'm using .NET core for a production app now. Team of 16. It's working beautifully. The data access is the bottleneck in 99% of what I have ever worked on, not the web framework. That is why Rails is so popular.
Re: How Raygun increased throughput 20x with .NET Core over Node.js
#53Here's what I read: they had a solution written in Node.js; they rewrote the solution in .NET Core; it was 20x faster. It's anecdotal, sure, and Microsoft prompted them to write it, and YMMV, but they did a thing and it had a remarkable result so they've remarked on it. It's not realistic to expect them to take the time to build a representative sample that doesn't expose any of their proprietary business logic; they…
The biggest problem with .NET Core imo is that .NET just seems to be permanently uncool, despite how good it is. Maybe one day this industry will be less fashion driven...
Yeah, but not everyone is a hype-train riding, super-cool hipster intent on switches languages every 6 months as some kind of fashion statement.
Re: How Raygun increased throughput 20x with .NET Core over Node.js
#54Re: How Raygun increased throughput 20x with .NET Core over Node.js
#55Earlier quoted context omitted.
The biggest problem with .NET Core imo is that .NET just seems to be permanently uncool, despite how good it is. Maybe one day this industry will be less fashion driven...
Yeah, but not everyone is a hype-train riding, super-cool hipster intent on switches languages every 6 months as some kind of fashion statement.
They aren't, but there's still a lot of irrational hate for anything even remotely associated with Microsoft, even amongst people who aren't chasing the hype. I can't really think of any other major general purpose platform that has this kind of PR problem.
Re: How Raygun increased throughput 20x with .NET Core over Node.js
#56I never trust any benchmark stories from Microsoft ever.
Well there are plenty of public not run by Microsoft benchmarks that show this same trend: https://www.techempower.com/benchmarks/#section=data-r14&hw=...
Re: How Raygun increased throughput 20x with .NET Core over Node.js
#57Re: How Raygun increased throughput 20x with .NET Core over Node.js
#58Re: How Raygun increased throughput 20x with .NET Core over Node.js
#59Earlier quoted context omitted.
"Your web server is not the bottleneck." - Highly depends on your setup. But removing any 3rd party libraries, and external requests. Generally .NET core is faster.
Honestly, add another machine and the problem is solved. youll be able to afford a team of programmers to rewrite your app in any language of your choosing by the time you feel the slow down. I'm using .NET core for a production app now. Team of 16. It's working beautifully. The data access is the bottleneck in 99% of what I have ever worked on, not the web framework. That is why Rails is so popular.
> Honestly, add another machine and the problem is solved. youll be able to afford a team of programmers to rewrite your app in any language of your choosing by the time you feel the slow down.
I understand your point, but your statement isn't true in all circumstances. It depends on your business model. Performance begins to matter more when the economics demand it. Say you're working on a game that has a free tier, or a service that offers some things for free and some things paid. Every customer hour costs you a certain amount, and you can expect a certain amount of revenue per customer hour on average. With this kind of a balance, a 20x performance difference can mean a fundamental shift in what kinds of business models can be profitable.
So for something like enterprise software, yeah, add another server. But for something like an MMO or 4Chan performance can be make or break. It's all about cost per user hour vs. revenue per user hour.
Re: How Raygun increased throughput 20x with .NET Core over Node.js
#60Earlier quoted context omitted.
Honestly, add another machine and the problem is solved. youll be able to afford a team of programmers to rewrite your app in any language of your choosing by the time you feel the slow down. I'm using .NET core for a production app now. Team of 16. It's working beautifully. The data access is the bottleneck in 99% of what I have ever worked on, not the web framework. That is why Rails is so popular.
> Honestly, add another machine and the problem is solved. youll be able to afford a team of programmers to rewrite your app in any language of your choosing by the time you feel the slow down. I understand your point, but your statement isn't true in all circumstances. It depends on your business model. Performance begins to matter more when the economics demand it. Say you're working on a game that has a free tier,…
The benchmark linked appears to be a 4x speedup that can potentially be attributed to the view engines used. It's really ridiculous to argue for 20x speedups without evidence of the deficit being in the web framework.
So lets take your hypothetical game example... What are your requests doing exactly? Are they returning cached content? If so, the caching policy is more important. If you're running a game, game state is probably changing constantly so you will need to connect to a database. Are you indexing things correctly, sharding, etc? Are you aware that Eve online runs python code?
You can point to any hypothetical scenario where you get a million users on a free tier, but then you will either have to get some funding or start charging for your services. In the case of the chat app Discord, they wrote their server architecture in Elixir, which runs on the Erlang VM called BEAM, which destroys .NET core at scale. Does that mean my team should stop using .NET core? No. I have to consider the knowledge base of the people I currently have as well as familiarity with deployment. The cost of the servers are a lot less important in the real world for 99% of applications any of us will write. I would even argue that it would be better to get to market faster with a product that scales poorly and to scale it as needed. Facebook was and still is written in PHP.