Sampling FrequencyĬertain tools, such as the CPU Usage tool and NET Object Allocation tool, allow you to adjust a sampling frequency. Some tools, such as the CPU Usage tool, allow you to pause data collection while the tool is running, so that you can limit the amount of data that's collected to the scenario that you are interested in analyzing.

Typically we recommend that you try to limit your traces to no longer than five minutes of performance data.

Profiling smaller durations results in less data, which is faster to analyze. When possible, leave Show external code disabled and ensure that you have the solution or workspace open for the diagsession you are analyzing. 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. 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 that's required to show results. User code is any code that's built by the open solution or open workspace. Many of the tools within the Performance Profiler and Diagnostic Tools window have a concept of user code versus external code. Instead, rely on symbols built locally for your project. If symbol loading is slowing down analysis, try turning off symbol servers and clear your symbol cache. Once downloaded, symbols are cached, which will speed up future analysis but still requires loading and analyzing the files. Progress on symbol loading can be seen in the Output window under the Diagnostic Tools heading. Currently, the profiler always automatically loads all symbols regardless of the automatic symbol loading preference. Enabling symbol servers or using the _NT_SYMBOL_PATH causes the profiler to request symbols for each loaded module in a report. The symbols settings found in the debugger options ( Debug > Options > Symbols or Tools > Options > Debugging > Symbols) have a significant impact on how long it takes to generate results in the tools. Below is a summary of certain settings and their impact on performance. Changing some settings can cause analysis to run quickly or cause additional wait times while processing results in tools. The Performance Profiler and Diagnostic Tools window in Visual Studio have many different settings which affect the overall performance of the tools.

Pinnacle profiler no longer loading