Find the Hot Path With dotnet-trace
Before we jump into optimising our application, we must make sure that the bottleneck we found is indeed an important one. If we optimise a part of the application that is seldomly used, we may waste a lot of time without improving the performance at all. The same is true for a part that is often used but faster than the real bottleneck somewhere else.
We can use the hot path to find the important spots in our application. But what is that and how do we find it?