Use Intel® GPA Graphics Frame Analyzer to identify bottlenecks in the graphics pipeline. Capture a stream (a sequence of frames), focus on a particular frame, and explore API calls and graphics resources of this frame.

To start frame analysis:

1. Run Graphics Monitor by double-clicking the Graphics Monitor icon in the taskbar notification area or on the desktop.
2. Specify the application for analysis by clicking the Browse button on the lower right and browsing to your application ().

   On Windows, you can use the sample application gpasample.exe.

3. Select the Stream startup mode from the drop-down menu on the lower right ().
4. Run the application by clicking the Start button ().

   The application launches in a separate window. By default, stream capture starts immediately when the application is started.

5. Complete stream capture by pressing L ().
6. Open the trace using the Open File ribbon of the Graphics Monitor window ().
   
   
   
   

   Multiframe View of Frame Analyzer opens.

7. For detailed analysis, open a frame that appears to perform poorly. For example, identify the longest frame by analyzing the GPU Time Elapsed metric, which shows the amount of time spent on frame rendering:
   1. On the GPU Time Elapsed track, click the longest frame ().
   2. Click the Open button on the lower left ().
   

   Profiling View window of Frame Analyzer opens.

8. Start analysis with the Advanced Profiling Mode, which allows you to identify potential bottlenecks. Click the Advanced Profiling Mode button on the top left.

   The API calls are grouped by bottlenecks on the Visualization () and API Log () panes. The first group of draw calls is the most impactful and time-consuming.

   
   
   
   
   

9. Start resolving issues with the most impactful bottleneck. Click the first group of draw calls either in the Visualization or API Log pane.

   The resources associated with this group of calls appear in the Resources pane. The Bottlenecks tab presents the graphics pipeline color-coded by bottleneck distribution. Red portions of the pipeline indicate main bottlenecks, and orange indicate secondary bottlenecks.

   
   
   
   
   
10. In the Bottlenecks tab, click the red bottleneck, for example, Local/Host Memory: Graphics-to-Memory Interface. The bottleneck cause, hints, and related metrics appear.
    
    
    
    
11. Once step 10 is done, close Graphics Frame Analyzer window.

As a result, you can identify potential bottlenecks of your application and get hints on how to resolve issues.