How Raygun increased throughput 20x with .NET Core over Node.js
1–10 of 61 posts
Re: How Raygun increased throughput 20x with .NET Core over Node.js
#2> when we started to look at .NET Core in early 2016, it became quite obvious that being able to asynchronously hand off to our queuing service greatly improved throughput. Unfortunately, at the time, Node.js didn’t provide an easy mechanism to do this, while .NET Core had great concurrency capabilities from day one.
This is a mildly maddening article - not because I have any emotional attachment to either platform - but because it never really gets to the heart of the matter. It's like they can tell us, but they'd have to kill us afterwards.
Re: How Raygun increased throughput 20x with .NET Core over Node.js
#3> when we started to look at .NET Core in early 2016, it became quite obvious that being able to asynchronously hand off to our queuing service greatly improved throughput. Unfortunately, at the time, Node.js didn’t provide an easy mechanism to do this, while .NET Core had great concurrency capabilities from day one. This is a mildly maddening article - not because I have any emotional attachment to either platform -…
I'm with ya. All hype, no details.
A 20X improvement cannot be attributed to .NET core, it must attributed substantially to some implementation/algorithmic issue that they resolved once they got to the .NET core platform. There's a big problem somewhere with node.js if it is 20X slower. If true, then its simply a bug or series of bugs to be fixed in node.js.
Re: How Raygun increased throughput 20x with .NET Core over Node.js
#4> when we started to look at .NET Core in early 2016, it became quite obvious that being able to asynchronously hand off to our queuing service greatly improved throughput. Unfortunately, at the time, Node.js didn’t provide an easy mechanism to do this, while .NET Core had great concurrency capabilities from day one. This is a mildly maddening article - not because I have any emotional attachment to either platform -…
I'm with ya. All hype, no details. A 20X improvement cannot be attributed to .NET core, it must attributed substantially to some implementation/algorithmic issue that they resolved once they got to the .NET core platform. There's a big problem somewhere with node.js if it is 20X slower. If true, then its simply a bug or series of bugs to be fixed in node.js.
Just a basic request/response with barely anything thing in it, shows the .NET core is faster than node.
https://stackoverflow.com/questions/43920942/unexpected-outc...
Obviously this isn't very scientific without a benchmark suite.
Re: How Raygun increased throughput 20x with .NET Core over Node.js
#5> when we started to look at .NET Core in early 2016, it became quite obvious that being able to asynchronously hand off to our queuing service greatly improved throughput. Unfortunately, at the time, Node.js didn’t provide an easy mechanism to do this, while .NET Core had great concurrency capabilities from day one. This is a mildly maddening article - not because I have any emotional attachment to either platform -…
I agree with you. A bold claim with very vague explanations makes it a bit hard to believe. I'd love to have more details on how they pulled that off.
Re: How Raygun increased throughput 20x with .NET Core over Node.js
#6Earlier quoted context omitted.
I'm with ya. All hype, no details. A 20X improvement cannot be attributed to .NET core, it must attributed substantially to some implementation/algorithmic issue that they resolved once they got to the .NET core platform. There's a big problem somewhere with node.js if it is 20X slower. If true, then its simply a bug or series of bugs to be fixed in node.js.
Just a basic request/response with barely anything thing in it, shows the .NET core is faster than node. https://stackoverflow.com/questions/43920942/unexpected-outc... Obviously this isn't very scientific without a benchmark suite.
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.
Re: How Raygun increased throughput 20x with .NET Core over Node.js
#7The fact that they were only getting 1k reqs/sec with Node gives me concern. It clearly shows something went wrong there very early on at a very fundamental level. By no means is Node the end-all be-all for performance by any measure, but you should definitely be getting much much higher throughput than 1k reqs/sec.
Simply booting up a single core http server should net you around 4-5k requests per second. Spin up an instance per core and you should be _at least_ in the 10k realm.
Re: How Raygun increased throughput 20x with .NET Core over Node.js
#8Earlier quoted context omitted.
Just a basic request/response with barely anything thing in it, shows the .NET core is faster than node. https://stackoverflow.com/questions/43920942/unexpected-outc... Obviously this isn't very scientific without a benchmark suite.
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.
Re: How Raygun increased throughput 20x with .NET Core over Node.js
#9> when we started to look at .NET Core in early 2016, it became quite obvious that being able to asynchronously hand off to our queuing service greatly improved throughput. Unfortunately, at the time, Node.js didn’t provide an easy mechanism to do this, while .NET Core had great concurrency capabilities from day one. This is a mildly maddening article - not because I have any emotional attachment to either platform -…
I'm with ya. All hype, no details. A 20X improvement cannot be attributed to .NET core, it must attributed substantially to some implementation/algorithmic issue that they resolved once they got to the .NET core platform. There's a big problem somewhere with node.js if it is 20X slower. If true, then its simply a bug or series of bugs to be fixed in node.js.
It may also be that it's easier to write in performance issues or bugs unintentionally with Node.
Re: How Raygun increased throughput 20x with .NET Core over Node.js
#10Earlier 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.
> But removing any 3rd party libraries, and external requests. Generally .NET core is faster.
Is that with reference to "faster than .Net regular" or "faster than node.js"?
You're right either way but I'm not sure that "it's just faster" is all that relevant. The "Just a basic request/response with barely anything thing in it" case removes anything of interest.
For any normal non-trivial, non-demo setup, the web server is fine. I would look at the performance of data stores and other backends. The performance of "asynchronously hand off to our queuing service" is most likely the overriding factor in a 20 or 30x increase.