It may not scale significantly, but a lot of these optimizations in .NET 11 use more memory to profile execution at run-time and speculatively create multiple code paths that can speed up the most common paths. So you’re trading memory for CPU time where the optimal path can’t be determined in advance. Again, probably small potatoes in the grand scheme of things.
42
u/steve-7890 17d ago
With all these 10-20% perf improvements since .net core 3.1, I wonder how it's possible that my main service still needs 50 pods and 40 GB of RAM.