Instead, make hot code paths asynchronous, call data access, I/O, and long-running patterns APIs asynchronously so that operations can be performed without affecting other processes. Also, avoid calling Task.Run as ASP.NET Core already runs threads in the normal thread pool so calling Task.Run would result in extra unnecessary Thread Pool Scheduling. These block the thread until the task is completed and wait for its completion. The problem with ASP.NET Core applications is blocking asynchronous execution by calling Task.Wait or Task.Result. Rather than waiting on the synchronous task to complete, it can start working on another thread. And you can achieve this through an Asynchronous API that handles thousands of requests without waiting on blocking calls. You should design you ASP.NET Core application to execute multiple processes simultaneously. So, while creating applications using ASP.NET core, always prefer the latest version of the ASP.NET Core as Microsoft always enhances the performance of the latest version in comparison to the previous. Net 5 is intended to release in November 2020 with simplified processing and optimized performance capabilities. ASP.NET Core 3.0 offered fast memory reading and writing, assembly unloads ability, and more. NET Core 2.1 added JIT compiler, support from compiled regular expressions, and benefitted Span tags, whereas 2.2 have support for HTTP/2.

Use the Latest VersionĮach version comes with a new upgrade, advanced features, and better performance.įor example. This blog is all about some important tips to improve the performance of your ASP.NET Core applications. However, it is important to perform timely checks to ensure your application is performing up to the mark. It provides developers a stable foundation for building web applications. There is one major reason, why ASP.NET core is a favourite framework for everyone - Its Performance

Eu3 how to get core tips