Performance is very important; it is a major factor for the success of any web application. ASP.NET Core 3.0 includes several enhancements that scale back memory usage and improve turnout. In this blog post, I provide 10 tips to help you improve the performance of ASP.NET Core 3.0 applications

LINQ is a powerful querying tool for .NET applications. There are certain techniques to follow when writing queries to make sure they run quickly and effectively. The following are a few things to consider when aiming to improve the performance of LINQ to Entities.

This article provides guidelines for performance best practices with ASP.NET Core.

BenchmarkDotNet, which is a tool to help us benchmark our code, not only by avoiding the use of the “old school” approach of writing a for wrapped in a Stopwatch to get some average running time, but adding more features on top of that, making the benchmarks not only simpler but more reliable.

IEnumerable is best suitable for working with in-memory collection (or local queries). IQueryable best suits for remote data source, like a database or web service (or remote queries). IQueryable is a very powerful feature that enables a variety of interesting deferred execution scenarios (like paging and composition based queries).

Specifically for '.NET Core' on Linux Performance Profiling and Diagnostics

Detect Blocking Calls in ASP.NET Core Applications. Blocking calls can lead to ThreadPool starvation. Outputs a warning to the log when blocking calls are made on the ThreadPool.

You may or may not have heard of this statistic from Google: 53% of mobile site visits leave a page that takes longer than three seconds to load. With that in mind, it’s important to make our site as responsive and quick as possible.