{"id":47452,"date":"2023-09-13T05:05:00","date_gmt":"2023-09-13T12:05:00","guid":{"rendered":"https:\/\/devblogs.microsoft.com\/dotnet\/?p=47452"},"modified":"2025-10-29T11:10:50","modified_gmt":"2025-10-29T18:10:50","slug":"performance-improvements-in-net-8","status":"publish","type":"post","link":"https:\/\/devblogs.microsoft.com\/dotnet\/performance-improvements-in-net-8\/","title":{"rendered":"Performance Improvements in .NET 8"},"content":{"rendered":"

I look forward to summer every year. Sun, beach, warm nights, and putting the finishing touches on the next version of .NET. It’s also the time I get to continue a tradition I started for myself back in 2017 of writing about the performance improvements that have gone into the latest .NET incarnation. A year ago that was Performance Improvements in .NET 7<\/a>, which followed similar posts for .NET 6<\/a>, .NET 5<\/a>, .NET Core 3.0<\/a>, .NET Core 2.1<\/a>, and .NET Core 2.0<\/a>.<\/p>\n

Since .NET 7<\/a> was released a year ago, you’ve likely been inundated with news about AI and ChatGPT. You may have even invested effort in using AI and\/or incorporated it into your applications<\/a>. And I got to wondering: could AI write this blog post for me? So I issued the following request to Bing Chat<\/a>:<\/p>\n

\n“You are an expert .NET developer with a penchant for pedagogy and a love of details. Write a treatise covering the most important performance improvements in .NET 8. The article should educate developers not just about what improvements were made, but also about why and how they were made so that developers can learn the relevant techniques and apply them in their own codebases. The article should also excite developers about the upcoming release, highlighting the very real benefits to upgrading their services, applications, and libraries to the new version. And the article should give credit to the myriad of developers that contributed significantly to the release, calling out the hundreds upon hundreds of pull requests that were merged to make .NET 8 the fastest .NET to date. The article should follow the style of the post about .NET 7 performance at https:\/\/devblogs.microsoft.com\/dotnet\/performance_improvements_in_net_7\/. Based on the extent and depth of everything to cover, it is estimated that the article should be around 200 pages in length, including all code samples and exposition.”\n<\/p><\/blockquote>\n

And the response?<\/p>\n

\n

“I’m sorry, but I can\u2019t write a 200-page treatise for you. That\u2019s beyond the scope of my capabilities and my chat settings. I can only generate short and concise content, such as summaries, snippets, or paragraphs. If you want to learn more about the performance improvements in .NET 8, you can check out some of the web search results I found for you. You can also read the official release notes and the GitHub issue tracker for more details. I hope you understand and appreciate my limitations. Thank you for your interest in .NET 8. \ud83d\ude0a”<\/p>\n<\/blockquote>\n

Fair enough (especially since, after writing this post and measuring the token count, it’s north of 300,000). And I’m happy with that outcome, because it means I still get to have the fun of writing this myself.<\/p>\n

Throughout the past year, as I was reviewing PRs in various .NET repos, I maintained a list of all the PRs that I might want to cover in this post, which is focused on the core runtime and libraries (Performance Improvements in ASP.NET Core 8<\/a> provides an in-depth focus on ASP.NET). And as I sat down to write this, I found myself staring at a daunting list of 1289 links. This post can’t cover all of them, but it does take a tour through more than 500 PRs, all of which have gone into making .NET 8 an irresistible release, one I hope you’ll all upgrade to as soon as humanly possible.<\/p>\n

.NET 7 was super fast. .NET 8 is faster.<\/p>\n

Table of Contents<\/h2>\n