Skip to content

Commit ebc60fd

Browse files
committed
add links
1 parent c7dfe20 commit ebc60fd

File tree

1 file changed

+14
-8
lines changed

1 file changed

+14
-8
lines changed

docs/profiling/profiling-feature-tour.md

Lines changed: 14 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -230,14 +230,6 @@ The tool shows each async operation in a list view. You can see information such
230230
![.NET Async Tool Stopped](../profiling/media/async-tool-opened.png ".NET Async Tool Stopped")
231231
::: moniker-end
232232

233-
## Examine application events
234-
235-
The generic [events viewer](../profiling/events-viewer.md) allows you to view the activity of your application through a list of events, such as module load, thread start, and system configurations, to help better diagnose how your application is performing right within the Visual Studio profiler. This tool is available in the Performance Profiler. Open the Performance Profiler by choosing **Debug** > **Performance Profiler** (or **Alt + F2**).
236-
237-
The tool shows each event in a list view. Columns provide information about each event, such as the event name, timestamp, and process ID.
238-
239-
![Event Viewer Trace](../profiling/media/prof-tour-events-viewer.png "Event Viewer Trace")
240-
241233
## Analyze database performance (.NET Core)
242234

243235
For .NET Core apps that use ADO.NET or Entity Framework Core, the [Database tool](../profiling/analyze-database.md) allows you to record the database queries that your application makes during a diagnostic session. You can then analyze information about individual queries in order to find places where your app's performance can be improved. This tool is available in the Performance Profiler. Open the Performance Profiler by choosing **Debug** > **Performance Profiler** (or **Alt + F2**).
@@ -254,6 +246,20 @@ The tool shows live values for each counter in a list view.
254246

255247
:::image type="content" source="../profiling/media/dotnet-counters-tool-collecting.png" alt-text=".NET Counter tool collecting.":::
256248

249+
## Examine application events
250+
251+
The generic [events viewer](../profiling/events-viewer.md) allows you to view the activity of your application through a list of events, such as module load, thread start, and system configurations, to help better diagnose how your application is performing right within the Visual Studio profiler. This tool is available in the Performance Profiler. Open the Performance Profiler by choosing **Debug** > **Performance Profiler** (or **Alt + F2**).
252+
253+
The tool shows each event in a list view. Columns provide information about each event, such as the event name, timestamp, and process ID.
254+
255+
![Event Viewer Trace](../profiling/media/prof-tour-events-viewer.png "Event Viewer Trace")
256+
257+
::: moniker range=">=vs-2022"
258+
## View custom events in the timeline graphs
259+
260+
You can programatically create custom events that appear as icons in the timeline graphs such as the CPU utilization and memory usage timeline graphs. For more information, see [Add user marks to timeline](../profiling/add-user-marks-to-timeline.md).
261+
::: moniker-end
262+
257263
## Analyze resource consumption (XAML)
258264

259265
In XAML apps, such as Windows desktop WPF apps and UWP apps, you can analyze resource consumption using the Application Timeline tool. For example, you can analyze the time spent by your application preparing UI frames (layout and render), servicing network and disk requests, and in scenarios like application startup, page load, and Window resize. To use the tool, choose **Application Timeline** in the Performance Profiler, and then choose **Start**. In your app, go through the scenario with a suspected resource consumption issue, and then choose **Stop collection** to generate the report.

0 commit comments

Comments
 (0)