Monitor Real-Time Performance with System Analyzer
System Analyzer vs Heads-up Display (HUD)
- Uses host/target (network) mode, enabling you to monitor performance on a remote system. This reduces performance impact on the application. You are recommended to use System Analyzer in the network mode to analyze graphics applications on Ultrabook™ devices, tablets, netbooks, or other devices with limited resources.
- Provides more detailed metrics resolution and the possibility to view more than four metrics at the same time, while also providing counter set selection and multiple other options. Using System Analyzer, you can compare an unlimited number of metrics with same measurement units by displaying them in the same chart, easily switch between metrics, and resize metrics charts for better analysis.
System Analysis Workflow
- Start your game from the Graphics MonitorOpen Graphics Monitor and select the application to run in the Graphics Monitor Launcher screen.This runs your game with the HUD overlay, quickly allowing you to analyze the performance data and capture frame and trace files.
- (Optional) Launch System AnalyzerReturn to the Graphics Monitor and click theConnect System Analyzerbutton next to your application.System Analyzer opens and attaches to your application. By default, System Analyzer starts in System View mode, which displays general system metrics. When it's attached to the application, System Analyzer provides more detailed metrics.
- Analyze metrics dataIntel GPA supports a wide variety of metrics. The metrics available for display might differ depending on your specific graphics device. Using real-time metrics, you can determine if your application is CPU- or GPU- bound, or identify the problematic area for further detailed analysis. For example, you can detect scenes, where:
- Frame rendering takes too long: analyze theFrame Timemetric.
- CPU and GPU workload is imbalanced: evaluate CPU and GPU load by analyzingGPU BusyandTarget App CPU Loadmetrics. Using these metrics, you can assume whether your performance issues are with the CPU or the GPU.
- After analyzing real-time metrics, you can proceed with more detailed analysis and try the following:
- If you suspect that your game is GPU-bound, capture frame files and use the Graphics Frame Analyzer to perform deeper analysis into exactly what is happening within a specific frame – see where in the rendering pipeline your game is spending its time, down to the render target or draw call level of detail. Check Frame Analysis for Desktop API Graphics Applications.
- If you suspect that there are issues in balancing your workloads across the CPU and GPU, capture and analyze trace files to get a task-based overview of your game across both the CPU and GPU domains.
- If you know that your game is CPU-bound, you might try using some CPU-specific tools to help improve your performance on the CPU, such as Intel® VTune™ Profiler. In particular, with multiple cores now being the rule rather than the exception, parallelizing your code can have a big impact on overall CPU performance.
Capture Frame/Stream/Trace for Deeper AnalysisTo perform deeper analysis with Frame Analyzer or Trace Analyzer, capture frame, stream, or trace files:
- In Graphics Monitor, specify an application for analysis.
- ChooseFrame,Stream, orTracemode from the launch modes drop-down menu on the lower right.
- Click theStartbutton to launch the application. A window with the game running opens.
- Choose one of the following methods to capture frame, stream, or trace:
- With HUD:
- To capture frame, pressCTRL + SHIFT + C
- To start/stop stream capture, pressL
- To capture trace, pressCTRL + SHIFT + T
- With System Analyzer:
- Return to the Graphics Monitor and click theConnect System Analyzerbutton next to your application.
- ClickCapture FrameorCapture Tracebuttons on the top left of the System Analyzer window.