.net 11 vs .net 10: 11% throughput lift on 110k-mau saas

Kirandeep Jassal published a side-by-side benchmark of .net 10 lts and the .net 11 preview on a multi-tenant analytics saas that serves about 110 k monthly active users and peaks at 3 200 requests per second [DevTo]. The test harness ran the same asp.net core workload on three runtimes: .net 9 (baseline), .net 10 (ga), and .net 11 preview [PrepStack]. Key results:

• throughput per instance: .net 10 delivered an 11% increase over .net 9; .net 11 preview added another 6-9% on top of .net 10.
• api p95 latency: dropped from 132 ms on .net 9 to 120 ms on .net 10, a 9% reduction; the preview shaved another 5-7%.
• working set: 415 mb on .net 9 fell to 380 mb on .net 10, with the preview a few megabytes lower.
• native aot cold start: 84 ms → 61 ms → ~55 ms.
• aot image size: 41 mb → 33 mb → ~30 mb.
• language version: c# 13 → c# 14 → c# 15 (preview). The migration from .net 9 to .net 10 required roughly 1.5 engineer-days for a 95 k loc codebase, mainly to adopt the new field keyword and extension members, which eliminated about 700 lines of boilerplate [DevTo]. The 11% throughput lift and smaller aot image size directly reduce cloud spend and improve pod density in kubernetes clusters. The low migration friction, with only 1.5 days of effort required, makes the upgrade to .net 10 lts a low-risk choice for teams with tight release schedules [PrepStack].