When you want to look at a performance or utilization issue more closely, stop collecting performance information, so that you can generate the report. Because this report takes some time to generate from the collected information, it's only available after the diagnostics session is done collecting information. You use this information to generate a more granular report of how your app utilizes the hardware. While your app runs under the GPU Usage tool, the diagnostics session also collects detailed information about graphics events that were run on the GPU. For example, further investigation might be warranted if you see a sudden drop in frame rate or a spike in GPU utilization. You use these graphs primarily to get a high-level idea of your app's performance, and to identify slow-downs that you might want to investigate. For the Frames per second graph, it's the opposite: your app exceeds the performance target when the graph is above the line, and it misses the target when the graph is below the line. In the Frame time graph, your app exceeds the performance target when the graph is below the line, and it misses the target when the graph is above the line.

The Frame time (ms) and Frames per second (FPS) graphs each have two red, horizontal lines that show performance targets of 60 and 30 frames per second. Each of these pieces of information is graphed independently, but they all use a common time-scale so that you can easily understand the relationships. The high-level information shown in real time includes frame timing, frame rate, and GPU usage. Not all performance and diagnostics tools can be used at the same time.Īt the bottom of the Performance and Diagnostics hub, select Start to run your app under the tools you selected.

Amd system monitor gpu 0