Skip to content

Commit a2d6cbd

Browse files
Merge pull request #10318 from MicrosoftDocs/main638572934887722842sync_temp
For protected branch, push strategy should use PR and merge to target branch method to work around git push error
2 parents ca37f53 + ce68280 commit a2d6cbd

File tree

2 files changed

+8
-2
lines changed

2 files changed

+8
-2
lines changed
Loading

docs/profiling/optimize-profiler-settings.md

Lines changed: 8 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
22
title: Optimizing Profiler settings
33
description: Learn how the Performance Profiler and Diagnostic Tools window in Visual Studio have many different settings that affect the overall performance of the tools.
4-
ms.date: 02/28/2023
4+
ms.date: 07/22/2024
55
ms.topic: how-to
66
helpviewer_keywords:
77
- Profiler, improve performance
@@ -28,7 +28,13 @@ Once downloaded, symbols are cached, which will speed up future analysis but sti
2828

2929
## Show External Code
3030

31-
Many of the tools within the **Performance Profiler** and **Diagnostic Tools** window have a concept of user code versus external code. User code is any code built by the open solution or open workspace. External code is anything else. By keeping the **Show external code** setting disabled, or **Show just my code** enabled, you allow the tools to aggregate external code to a single first level frame, greatly reducing the amount of processing required to show results. This allows users to see what was called in external code that created the slow down while keeping the data to be processed to a minimum. When possible, leave **Show external code** disabled and ensure that you have the solution or workspace open for the diagsession you're analyzing.
31+
Many of the tools within the **Performance Profiler** and **Diagnostic Tools** window have a concept of user code versus external code. User code is any code built by the open solution or open workspace. External code is anything else. By keeping the **Show just my code** setting enabled, or the **Show external code** setting disabled, you allow the tools to aggregate external code to a single first level frame, greatly reducing the amount of processing required to show results. This allows users to see what was called in external code that created the slow down while keeping the data to be processed to a minimum. When possible, enable **Show external code** and make sure that you have the solution or workspace open for the *.diagsession* file that you're analyzing.
32+
33+
For most profiling tools, the user code option is present in the settings for the summary page of the report.
34+
35+
::: moniker range=">=vs-2022"
36+
![Screenshot of Show just my code option.](../profiling/media/vs-2022/cpu-usage-show-just-my-code.png "Screenshot of Show just my code option.")
37+
::: moniker-end
3238

3339
## Trace Duration
3440

0 commit comments

Comments
 (0)