From 85775b2d29adb2ba915abb90c57a803e20e95d15 Mon Sep 17 00:00:00 2001 From: Muhammad Umair Irshad Date: Mon, 6 May 2019 16:30:49 +0100 Subject: [PATCH] Typo in url for thread pool doc page (#12258) --- aspnetcore/performance/performance-best-practices.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/aspnetcore/performance/performance-best-practices.md b/aspnetcore/performance/performance-best-practices.md index 858d7cfecf..f0455d8209 100644 --- a/aspnetcore/performance/performance-best-practices.md +++ b/aspnetcore/performance/performance-best-practices.md @@ -38,7 +38,7 @@ A common performance problem in ASP.NET Core apps is blocking calls that could b * Call data access and long-running operations APIs asynchronously. * Make controller/Razor Page actions asynchronous. The entire call stack is asynchronous in order to benefit from [async/await](/dotnet/csharp/programming-guide/concepts/async/) patterns. -A profiler, such as [PerfView](https://github.com/Microsoft/perfview), can be used to find threads frequently added to the [Thread Pool](/windows/desktop/procthread/thread-pool). The `Microsoft-Windows-DotNETRuntime/ThreadPoolWorkerThread/Start` event indicates a thread added to the thread pool. +A profiler, such as [PerfView](https://github.com/Microsoft/perfview), can be used to find threads frequently added to the [Thread Pool](/windows/desktop/procthread/thread-pools). The `Microsoft-Windows-DotNETRuntime/ThreadPoolWorkerThread/Start` event indicates a thread added to the thread pool. ## Minimize large object allocations