Analyze GPU-bound Applications with Graphics Frame Analyzer
Capture and Open a Frame/stream.
- Run the Graphics Monitor on your system, specify an app for analysis, and choose one of the following startup modes:
- Stream mode(recommended) to capture a stream. A stream is a set of consecutive frames.
- Frame modeto capture a single frame
- ClickStartto launch the graphics application as described in Launch the Application topic. The application starts running with the Heads-Up Display overlay.
- Capture a frame by pressingCtrl+Shift+C. You can capture as many frames as you need without stopping and restarting the application using the key combination.If you find it difficult to capture a frame at the right moment, set up a trigger to capture a frame automatically when a certain condition is met (for example, when the frame rate drops below 10 FPS). Refer to Set Up a Trigger topic for more details.Streams are created automatically upon startup. During the capture, all the overrides are turned off. When the capture is complete, the HUD shows a message with the file name or possible errors, if any.Capture streams manually in DirectX* and Vulkan* APIs by enabling theDeferred Stream Captureoption in theStreamtab of the Graphics MonitorOptions. The key shortcut is specified in the Shortcuts tab (the default key is "L").
- Open the captured frame/stream using any of these options:
- From theOpen Filedialog box in the Graphics Monitor. Drag the pane to the left to see more captured frames/streams.
- Launch the Graphics Frame Analyzer and find the captured fragment in the Open Frame Capture window. Sort and filter the captured frames/streams, to find the ones you need.
Locate Bottlenecks in Separate Heavy Calls
- Click on a draw call.
- Use theMetrics Paneon the right to examine domains for the selected graphics API functions in the form of call rendering stages, processes and operations.Domains marked green perform well and do not need optimizing. Red and yellow ones indicate bottlenecks:
- Domains marked red indicate a block with a primary bottleneck for the current selection or entire frame, if nothing is selected. Analyze them in the first place, as they take up most of the resources.
- Yellow domains denote a block with secondary or potential bottleneck.
- To see details and general recommendations for possible problem solving, click the functions and read their description below.Read more about optimizing graphics functions in Intel® Graphics Performance Analyzers Cookbook
Explore the Shader Program
- Based on the information from the Shader Profiler, you can locate hotspots in your shader code and resolve any shader performance issues.Read more about optimizing the Shader in Shader Execution topic of Intel GPA Cookbook.
- After Shader Profiler analysis, you can look into other resources by pressingShow All Resources.