Summary view
Applies to: 
Visual Studio 
Visual Studio for Mac
Note
This article applies to Visual Studio 2017. If you're looking for the latest Visual Studio documentation, see Visual Studio documentation. We recommend upgrading to the latest version of Visual Studio. Download it here
The Summary view displays information about the most performance-expensive functions or objects in a profiling run. This view provides a timeline graph and two or more lists of the most expensive functions or objects based on the performance metrics of the profiling method. The data in this view depends on the profiling method that was used (sampling, instrumentation, or concurrency) and whether .NET memory allocation was collected.
For all Summary views except the Summary view of concurrency data, the timeline graph in the Summary view shows the processor (CPU) utilization of the profiled application over the time that the profiling occurred.
If you specify a segment of time on the graph, you can reanalyze the data for that segment or zoom the timeline display to the segment that you specified. For more information, see How to: Filter report views from the Summary Timeline.
You can click a function in a Summary view list to open the Function Details view for the function. You also can right-click the function for other view options.
To modify the number of items that appear in Summary view lists, open the Tools menu, point to Options, and then click Performance Tools. Under General settings, modify the Number of functions in Summary view setting.
Notifications links
You can click links in the Notification list to set display options for the report. The list is to the right of the timeline graph.
| Option | Description |
|---|---|
| Show Non-User Code Show Just My Code |
Not available for native code or for profiling data that was collected by using the instrumentation method. Toggles between displaying only data from user code (Show Just My Code) and displaying data from all code, including system code (Show Non-User Code). By default, data is limited to user code. To change the setting, see How to: Filter profiling tools report views to display Just My Code. |
| View Guidance | Displays performance rule warnings in the Error List window. For more information, see Use performance rules to analyze data |
Report
You can click links in the Report list to open different views and to compare, save, or filter the report. The list is to the right of the timeline graph.
| Option | Description |
|---|---|
| Show Trimmed Call Tree | Displays the most expensive execution paths in the Call Tree View. For more information, see Call Tree view. |
| Show Hot Lines | Not available for profiling data that was collected by using the instrumentation method. Displays the most expensive source code lines in Lines View. For more information, see Lines view. |
| Compare Reports | Displays the Select analysis files for comparison dialog box where you can specify another profiling data file to compare to the current file. For more information, see Compare performance data files. |
| Export Report Data | Displays the Export Report dialog box where you can specify one or more report views to save as comma-separated value (.csv) or .xml files. For more information, see How to: Export profiling tools reports. |
| Save Analyzed Report | Saves the current profiling data file as a .vsps file, which opens more quickly in the interface for Visual Studio. For more information, see How to: Save analyzed profiling data files. |
| Filter Report Data | Displays the profiling report filter pane where you can specify criteria to restrict the data in the report view. For more information, see Performance report view filter |
| Toggle Full Screen | Toggles full-screen mode for the report view. |