Identify Basic GPU-CPU Bound Scenarios
- Tool:Intel® GPAGraphics Trace Analyzer
- Operating System: Windows*
- GPU: Any
- API: DirectX* 9-12, Vulkan*
How to Start Analysis
- Launch theIntel® GPAGraphics Monitoron your target system.
- Capture a sample trace. A trace contains performance data connected with your application and system.
- Open the captured trace in theGraphics Trace Analyzerto explore performance events in GPU/CPU queues and VSync events generated by a window display manager.
Analyze GPU and CPU queues
Typical GPU Bound Scenario
- Hardware queue is completely busy executing command buffers and has no visible gaps.
- Driver queue continuously accumulates command buffers waiting for the execution on the GPU.
- Average command buffer execution time exceeds the desired limit based on the expected FPS rate.
VSync Bound Scenario
- Hardware queue has visible gaps, indicating that the GPU is not fully busy.
- Driver queue has visible gaps, indicating that the CPU part of graphics workload is low enough.
- Frame time is shorter than VSync intervals.
Typical CPU Bound Scenario
- Hardware queue size is small and has visible gaps. This means that the GPU is idle most of the time.
- Driver queue size is big enough.
Multi-Process GPU Utilization Scenario
- More than one graphics application run simultaneously.
- GPU queue is full and contains packages from multiple processes.