For additional details and documentation, see Intel® Graphics Performance Analyzers.

This video will show you how to perform live system-level analysis on your Microsoft DirectX* application using the Intel® Graphics Performance Analyzers Heads-Up Display.

Once you launch your application through Graphics Monitor, you’ll see the HUD in the top-left corner of the application window.

It shows the applications graphics API, resolution, and current frame rate.

Using the HUD you can also examine various CPU, GPU, graphics API, and system metrics in real time.

Press CTRL+F1 to view 4 selected metrics while your application is running. The current metric values are show in white, while red and green metric values are the lowest and highest values, respectively.

If you would like to change the metric values, open the Graphics Monitor window and select Options. Select HUD Metrics and either remove or add metrics accordingly - making sure not to exceed 4 metrics. Metrics will automatically update within the HUD.

Perform simple graphics experiments or overrides to quickly identify performance bottlenecks. Press CTRL+F1 again to view the list of available overrides and their respective keyboard shortcuts.

You do not need to modify the application source code or recompile the application to view the outcome of any particular override.

To understand if your application is CPU or GPU bound, you can disable all draw calls using the keyboard shortcut: CTRL+ALT+N.

If you notice that your frame rate dramatically increases, it is likely that your application is GPU bound. You should continue your analysis in the Frame Analyzer tool.

Pressing CTRL+ALT+K, you can disable all overrides and return the application to its original state.

To capture a frame to be used in offline mode within the Graphics Frame Analyzer  tool press CTRL+SHIFT+C .

If you discover that your application is CPU bound, you should continue analysis using Trace Analyzer. To do so, capture a trace file by pressing CTRL+SHIFT+T. Trace captures  collect data for a trailing 5 seconds.

You are now ready to perform offline analysis within Frame Analyzer or Trace Analyzer.