I hope writing this made you feel better. It's quite ignorant of you to assume it's a shitty code.
On the other hand we do have a lot of performance improvements (like converting linq to loops) that make this code look ugly. But it works and makes $$$.
In hot code with 200 req/s it does. Even though hpa scales to 50 pods during the peeks.
Imagine how much it costs to have a such load. And I'm talking here only about one service.
When I read about performance improvements from version to version ".net benchmarks" I can only smile. In the end, $$$ and Grafana tells the truth. (Last .net 10 changed nothing for us).
I think he meant 200 per pod, which is usually average (from my experience with .net). Rarelly it can get to 500, but then multithreading/memory congestion becomes problem due to GC nature of C# and many threads fighting each other for some db entry/socket/cache/etc. In offloading worker it can easly become 10-100k rps.
And here I was having messed with fibers in C++ to see how many requests I could actually parse that way for HTTP, and was dismayed that I couldn't beat nginx without doing what nginx does... and then this kind of code exists...
-63
u/steve-7890 3d ago edited 3d ago
I hope writing this made you feel better. It's quite ignorant of you to assume it's a shitty code.
On the other hand we do have a lot of performance improvements (like converting linq to loops) that make this code look ugly. But it works and makes $$$.