CPU/GPU Concurrency analysis type is intended for platform analysis of applications that use a Graphics Processing Unit (GPU) for rendering, video processing, and computations. Use this analysis type as a starting point to understand the code execution on the various CPU and GPU cores in your system and identify whether your target application is GPU or CPU bound. The tool infrastructure automatically aligns clocks across all cores in the entire system so that you can analyze some CPU-based workloads together with GPU-based workloads within a unified time domain.
Use the CPU/GPU Concurrency analysis to:
Explore GPU usage and analyze a software queue for GPU engines at each moment of time
Correlate CPU and GPU activity and identify whether your application is GPU or CPU bound
Identify GPU and CPU application frame rate and how it depends on vertical synchronization
Explore the performance of your application per selected GPU metrics over time
Analyze execution of Intel Media SDK tasks over time (for Linux targets only)
Explore your application performance for user tasks created with Intel ITT API
To run the CPU/GPU Concurrency analysis, explore:
Configuration Options
To view configuration options for the CPU/GPU Concurrency analysis:
Click the
New Analysis toolbar button.
The Analysis Type window opens.
From the left pane, select Platform Analysis > CPU/GPU Concurrency.
The CPU/GPU Concurrency configuration pane opens on the right displaying predefined collection options for this analysis. To modify an option or change the list of collected hardware events, create a new custom analysis type.
Note
You may generate the command line for this configuration using the Command Line... button at the bottom.
Viewpoints
VTune Amplifier runs the analysis and opens the data in the Hotspots viewpoint providing various platform data in the following windows:
Platform window displays overtime data as GPU usage on a software queue, CPU time usage, OpenCL™ kernels data, Memory Bandwidth, and CPU Frequency.
Graphics window displays CPU and GPU usage data per thread.
What's Next
If you explored the CPU/GPU Concurrency analysis results and discovered that your application is GPU-bound, you may proceed with the GPU Hotspots analysis for detailed GPU analysis.