3 ms·
I thought this was a really good post[0] on the networking performance potential of .NET. [0]: https://dzone.com/articles/how-raygun-increased-throughput-by-20
by kuwze 8y ago
I thought this was a really good post[0] on the networking performance potential of .NET.
[0]: https://dzone.com/articles/how-raygun-increased-throughput-by-2000-with-net-c https://dzone.com/articles/how-raygun-increased-throughput-b...
- kjeetgill 8y agoSort of? It's interesting work but I don't know if I'd frame it as "networking performance potential of .NET". The title is "How Raygun Increased Throughput by 2,000% With .NET Core (Over Node.js)". From the article: > In terms of EC2, we utilized c3.large nodes for both the Node.js deployment and then for the .NET Core deployment. Both sit as backends behind an NGINX instance and are managed using scaling groups in EC2 sitting behind a standard AWS load balancer (ELB). They're comparing their Node.js vs C# versions behind ELB and NGINX. It's barely touching the networking part of the stack directly. They gains are almost definitely all from a stronger compiler story and a concurrency story. They say themselves: > Node is a productive environment and has a huge ecosystem around it, but frankly, it hasn’t been designed for performance.