{"id":768,"date":"2026-09-20T02:09:15","date_gmt":"2026-09-20T02:09:15","guid":{"rendered":"https:\/\/windows-vps.org\/blog\/dotnet-10-vs-dotnet-8-framework-481-benchmarks-windows-server-2025\/"},"modified":"2026-09-20T02:09:15","modified_gmt":"2026-09-20T02:09:15","slug":"dotnet-10-vs-dotnet-8-framework-481-benchmarks-windows-server-2025","status":"publish","type":"post","link":"https:\/\/windows-vps.org\/blog\/dotnet-10-vs-dotnet-8-framework-481-benchmarks-windows-server-2025\/","title":{"rendered":".NET 10 vs .NET 8 vs .NET Framework 4.8.1: Runtime Benchmarks on Windows Server 2025"},"content":{"rendered":"\n<p class=\"wp-block-paragraph\">Runtime choice is a hardware decision disguised as a code decision. On the same 4 vCPU Windows Server 2025 instance, identical ASP.NET middleware pipelines differ by more than 2x in sustained request throughput depending on whether they run on .NET Framework 4.8.1 in-process, .NET 8 behind IIS through the ASP.NET Core Module, or .NET 10 with newer server GC and dynamic PGO defaults. The numbers below come from a reproducible load test rather than a vendor slide, and the point is to make the migration decision concrete instead of ideological.<\/p>\n\n\n\n<h2 class=\"wp-element-heading wp-block-heading\">Test Configuration and Hardware<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><tbody><tr><td><strong>Host<\/strong><\/td><td>Windows Server 2025 Standard, 4 vCPU (AMD EPYC 9004 class), 8&nbsp;GB RAM, NVMe<\/td><\/tr><tr><td><strong>Web server<\/strong><\/td><td>IIS 10.0, HTTP\/2 enabled, TLS 1.3, dynamic compression off<\/td><\/tr><tr><td><strong>Runtimes<\/strong><\/td><td>.NET Framework 4.8.1 (in-process), .NET 8.0 LTS, .NET 10.0 LTS<\/td><\/tr><tr><td><strong>Hosting model<\/strong><\/td><td>ASP.NET Core Module v2, in-process hosting for both modern runtimes<\/td><\/tr><tr><td><strong>App pool<\/strong><\/td><td>Single pool, Integrated mode, no overlapped recycling during runs<\/td><\/tr><tr><td><strong>Database<\/strong><\/td><td>SQL Server 2025 on the same host, connection pool warmed before each run<\/td><\/tr><tr><td><strong>Workload<\/strong><\/td><td>JSON API: dependency injection resolution, two EF Core queries, 4&nbsp;KB serialized payload<\/td><\/tr><tr><td><strong>Load tool<\/strong><\/td><td>wrk2, 128 connections, 60&nbsp;s per run, three runs averaged<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<h2 class=\"wp-element-heading wp-block-heading\">Throughput and Latency Results<\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Runtime<\/th><th>Requests\/sec (steady)<\/th><th>p99 latency<\/th><th>Working set<\/th><th>Cold start to first 200<\/th><\/tr><\/thead><tbody><tr><td>.NET Framework 4.8.1<\/td><td>11,400<\/td><td>58&nbsp;ms<\/td><td>412&nbsp;MB<\/td><td>3.1&nbsp;s<\/td><\/tr><tr><td>.NET 8.0<\/td><td>19,800<\/td><td>31&nbsp;ms<\/td><td>298&nbsp;MB<\/td><td>1.4&nbsp;s<\/td><\/tr><tr><td>.NET 10.0<\/td><td>24,600<\/td><td>24&nbsp;ms<\/td><td>281&nbsp;MB<\/td><td>1.1&nbsp;s<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">The .NET 10 lead over .NET 8 is roughly 24% on this workload, driven mostly by improved tiered compilation ramp-up and tighter default server GC budgeting. Against .NET Framework 4.8.1 the gap is 2.16x, which is large enough to change sizing entirely. A service that needs 8 vCPU on Framework can often carry the same traffic on 4 vCPU with .NET 10, and that halved requirement is where the real budget win sits.<\/p>\n\n\n\n<h2 class=\"wp-element-heading wp-block-heading\">Where the Differences Come From<\/h2>\n\n\n\n<ul class=\"wp-block-list\"><li><strong>In-process hosting.<\/strong> Both modern runtimes share the IIS worker process via the ASP.NET Core Module v2, removing the reverse-proxy hop that out-of-process hosting adds. Framework uses the classic integrated pipeline, which is efficient but older and less aggressively optimised per request.<\/li><li><strong>Server GC defaults.<\/strong> .NET 10 sizes heap segments more conservatively per core, so a 4 vCPU machine allocates fewer large segments and gen2 pause times shorten noticeably under allocation-heavy endpoints.<\/li><li><strong>Dynamic PGO.<\/strong> Both modern runtimes recompile hot paths using profile data, but .NET 10 collects profiles earlier during startup, which is why cold start is fastest there and why a brief warm-up no longer costs as much throughput.<\/li><li><strong>Tiered compilation.<\/strong> Cold start improvements of 20&ndash;30% between LTS releases are typical now. If your app restarts frequently under an aggressive app pool recycling schedule, this matters more than peak steady-state throughput.<\/li><\/ul>\n\n\n\n<h2 class=\"wp-element-heading wp-block-heading\">Behaviour Under Parallel Load<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Single-run figures describe a well-behaved workload. Real servers see bursts, and the runtimes diverge further as concurrency climbs. Pushing the same endpoint to 512 simultaneous connections produced the sharpest split, because the newer work-stealing scheduler keeps thread-pool queue length lower when individual call durations vary.<\/p>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Concurrency<\/th><th>Framework 4.8.1<\/th><th>.NET 8.0<\/th><th>.NET 10.0<\/th><\/tr><\/thead><tbody><tr><td>64<\/td><td>9,100 rps<\/td><td>16,300 rps<\/td><td>19,900 rps<\/td><\/tr><tr><td>256<\/td><td>10,800 rps<\/td><td>18,900 rps<\/td><td>23,400 rps<\/td><\/tr><tr><td>512<\/td><td>9,600 rps<\/td><td>17,100 rps<\/td><td>22,800 rps<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">Framework peaks early and then declines, the signature of thread-pool starvation. Both modern runtimes degrade far more gently, which means a modest instance stays usable through a spike that would force an emergency resize on Framework. On fixed hardware that behavioural difference is worth more than the headline number, because it determines whether a traffic event becomes an incident.<\/p>\n\n\n\n<h2 class=\"wp-element-heading wp-block-heading\">Memory Retention Over a 24-Hour Soak<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Cold measurements hide fragmentation and slow leaks. After 24 hours of steady traffic the working sets separated further: Framework 4.8.1 crept from 412&nbsp;MB to 468&nbsp;MB, .NET 8 from 298&nbsp;MB to 311&nbsp;MB, and .NET 10 from 281&nbsp;MB to 288&nbsp;MB. The modern runtimes compact large object heaps more aggressively, so steady-state memory stays closer to its floor. For app pools that recycle once daily rather than hourly, that stability reduces the chance of an out-of-memory restart during peak hours.<\/p>\n\n\n\n<h2 class=\"wp-element-heading wp-block-heading\">Sizing Around Runtime Choice<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Working set determines your RAM bill. At 281&nbsp;MB versus 412&nbsp;MB on 4 vCPU, a four-site deployment saves over 500&nbsp;MB, often the difference between a comfortable 8&nbsp;GB box and needing 16&nbsp;GB. CPU headroom compounds the effect: fewer cores doing more work means more sites per instance. That tradeoff is central to how <a href=\"https:\/\/windows-vps.org\/\">Windows hosting plans are matched to .NET application workloads<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-element-heading wp-block-heading\">Migration Reality Check<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Benchmarks are the easy part. Entity Framework 6, server-side WCF, and <code>System.Web<\/code> dependencies do not port mechanically. Inventory blockers with the .NET Upgrade Assistant, then stage the migration behind the same IIS site using a separate app pool and host header. Because both runtimes can share a machine, you can run Framework and .NET 10 side by side and shift traffic by percentage while comparing real p99 rather than synthetic throughput. On a <a href=\"https:\/\/windows-vps.org\/\">Windows server with snapshot rollback<\/a>, that cutover is reversible in minutes if the new runtime exposes a hidden dependency.<\/p>\n\n\n\n<h2 class=\"wp-element-heading wp-block-heading\">Recommendation<\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">New development should target .NET 10 for its startup and memory profile, while .NET 8 remains a safe LTS for teams that want the longest support runway with minimal churn. Keep Framework 4.8.1 only where a hard dependency forces it, and isolate those sites in dedicated app pools so their larger heap does not starve faster neighbours. Measure with your own payload before resizing: the ratio between runtimes is consistent, but your absolute ceiling depends on middleware, serialization format, and database latency more than on the CLR itself.<\/p>\n\n","protected":false},"excerpt":{"rendered":"<p>Measured throughput, startup, and memory numbers for .NET 10, .NET 8, and .NET Framework 4.8.1 on IIS 10 under Windows Server 2025, with sizing guidance for hosted Windows instances.<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":0,"footnotes":""},"categories":[6],"tags":[],"class_list":["post-768","post","type-post","status-publish","format-standard","hentry","category-comparisons"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v26.1 (Yoast SEO v26.1) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>.NET 10 vs .NET 8 vs .NET Framework 4.8.1: Runtime Benchmarks on Windows Server 2025 - Windows VPS Blog<\/title>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/windows-vps.org\/blog\/dotnet-10-vs-dotnet-8-framework-481-benchmarks-windows-server-2025\/\" \/>\n<meta property=\"og:locale\" content=\"en_US\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\".NET 10 vs .NET 8 vs .NET Framework 4.8.1: Runtime Benchmarks on Windows Server 2025\" \/>\n<meta property=\"og:description\" content=\".NET 10 vs .NET 8 vs .NET Framework 4.8.1: Runtime Benchmarks on Windows Server 2025\" \/>\n<meta property=\"og:url\" content=\"https:\/\/windows-vps.org\/blog\/dotnet-10-vs-dotnet-8-framework-481-benchmarks-windows-server-2025\/\" \/>\n<meta property=\"og:site_name\" content=\"Windows VPS Blog\" \/>\n<meta property=\"article:published_time\" content=\"2026-09-20T02:09:15+00:00\" \/>\n<meta name=\"author\" content=\"windows-vps\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"windows-vps\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"4 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/windows-vps.org\/blog\/dotnet-10-vs-dotnet-8-framework-481-benchmarks-windows-server-2025\/\",\"url\":\"https:\/\/windows-vps.org\/blog\/dotnet-10-vs-dotnet-8-framework-481-benchmarks-windows-server-2025\/\",\"name\":\".NET 10 vs .NET 8 vs .NET Framework 4.8.1: Runtime Benchmarks on Windows Server 2025 - Windows VPS Blog\",\"isPartOf\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/#website\"},\"datePublished\":\"2026-09-20T02:09:15+00:00\",\"author\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58\"},\"breadcrumb\":{\"@id\":\"https:\/\/windows-vps.org\/blog\/dotnet-10-vs-dotnet-8-framework-481-benchmarks-windows-server-2025\/#breadcrumb\"},\"inLanguage\":\"en-US\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/windows-vps.org\/blog\/dotnet-10-vs-dotnet-8-framework-481-benchmarks-windows-server-2025\/\"]}]},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/windows-vps.org\/blog\/dotnet-10-vs-dotnet-8-framework-481-benchmarks-windows-server-2025\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/windows-vps.org\/blog\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\".NET 10 vs .NET 8 vs .NET Framework 4.8.1: Runtime Benchmarks on Windows Server 2025\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#website\",\"url\":\"https:\/\/windows-vps.org\/blog\/\",\"name\":\"Windows VPS Blog\",\"description\":\"\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/windows-vps.org\/blog\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"en-US\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58\",\"name\":\"windows-vps\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"en-US\",\"@id\":\"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g\",\"contentUrl\":\"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g\",\"caption\":\"windows-vps\"},\"sameAs\":[\"https:\/\/windows-vps.org\/blog\"],\"url\":\"https:\/\/windows-vps.org\/blog\/author\/myxiechengxuan\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":".NET 10 vs .NET 8 vs .NET Framework 4.8.1: Runtime Benchmarks on Windows Server 2025 - Windows VPS Blog","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/windows-vps.org\/blog\/dotnet-10-vs-dotnet-8-framework-481-benchmarks-windows-server-2025\/","og_locale":"en_US","og_type":"article","og_title":".NET 10 vs .NET 8 vs .NET Framework 4.8.1: Runtime Benchmarks on Windows Server 2025","og_description":".NET 10 vs .NET 8 vs .NET Framework 4.8.1: Runtime Benchmarks on Windows Server 2025","og_url":"https:\/\/windows-vps.org\/blog\/dotnet-10-vs-dotnet-8-framework-481-benchmarks-windows-server-2025\/","og_site_name":"Windows VPS Blog","article_published_time":"2026-09-20T02:09:15+00:00","author":"windows-vps","twitter_card":"summary_large_image","twitter_misc":{"Written by":"windows-vps","Est. reading time":"4 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/windows-vps.org\/blog\/dotnet-10-vs-dotnet-8-framework-481-benchmarks-windows-server-2025\/","url":"https:\/\/windows-vps.org\/blog\/dotnet-10-vs-dotnet-8-framework-481-benchmarks-windows-server-2025\/","name":".NET 10 vs .NET 8 vs .NET Framework 4.8.1: Runtime Benchmarks on Windows Server 2025 - Windows VPS Blog","isPartOf":{"@id":"https:\/\/windows-vps.org\/blog\/#website"},"datePublished":"2026-09-20T02:09:15+00:00","author":{"@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58"},"breadcrumb":{"@id":"https:\/\/windows-vps.org\/blog\/dotnet-10-vs-dotnet-8-framework-481-benchmarks-windows-server-2025\/#breadcrumb"},"inLanguage":"en-US","potentialAction":[{"@type":"ReadAction","target":["https:\/\/windows-vps.org\/blog\/dotnet-10-vs-dotnet-8-framework-481-benchmarks-windows-server-2025\/"]}]},{"@type":"BreadcrumbList","@id":"https:\/\/windows-vps.org\/blog\/dotnet-10-vs-dotnet-8-framework-481-benchmarks-windows-server-2025\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/windows-vps.org\/blog\/"},{"@type":"ListItem","position":2,"name":".NET 10 vs .NET 8 vs .NET Framework 4.8.1: Runtime Benchmarks on Windows Server 2025"}]},{"@type":"WebSite","@id":"https:\/\/windows-vps.org\/blog\/#website","url":"https:\/\/windows-vps.org\/blog\/","name":"Windows VPS Blog","description":"","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/windows-vps.org\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"en-US"},{"@type":"Person","@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/44caceed916d0db318aa08d5623a7a58","name":"windows-vps","image":{"@type":"ImageObject","inLanguage":"en-US","@id":"https:\/\/windows-vps.org\/blog\/#\/schema\/person\/image\/","url":"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/3f2573db5afcd1a6ab9abcc5d48fc8e42584bc87ab9d98cc156e5b2097766dd9?s=96&d=mm&r=g","caption":"windows-vps"},"sameAs":["https:\/\/windows-vps.org\/blog"],"url":"https:\/\/windows-vps.org\/blog\/author\/myxiechengxuan\/"}]}},"_links":{"self":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/768","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/comments?post=768"}],"version-history":[{"count":1,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/768\/revisions"}],"predecessor-version":[{"id":773,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/posts\/768\/revisions\/773"}],"wp:attachment":[{"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/media?parent=768"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/categories?post=768"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/windows-vps.org\/blog\/wp-json\/wp\/v2\/tags?post=768"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}