Download Profiler User's Guide - Computer Science and Engineering
Transcript
nvprof GPU Device 0: "GeForce GT 640M LE" with compute capability 3.0 MatrixA(320,320), MatrixB(640,320) Computing result using CUDA Kernel... done Performance= 23.73 GFlop/s, Time= 5.523 msec, Size= 131072000 Ops, WorkgroupSize= 1024 threads/block Checking computed result for correctness: OK Note: For peak performance, please refer to the matrixMulCUBLAS example. ==60642== Profiling application: matrixMul ==60642== Profiling result: Device Context Stream Kernel branch (0) GeForce GT 640M 1 2 void matrixMulCUDA<i 35200 GeForce GT 640M 1 2 void matrixMulCUDA<i 35200 <...more output...> branch (1) 35200 35200 --aggregate-mode also applies to metrics. However some metrics are only available in aggregate mode and some are only available in non-aggregate mode. 3.2. Profiling Controls 3.2.1. Timeout A timeout (in seconds) can be provided to nvprof. The CUDA application being profiled will be killed by nvprof after the timeout. Profiling result collected before the timeout will be shown. Timeout starts counting from the moment the CUDA driver is initialized. If the application doesn't call any CUDA APIs, timeout won't be triggered. 3.2.2. Concurrent Kernels Concurrent-kernel profiling is supported, and is turned on by default. To turn the feature off, use the option --concurrent-kernels off. This forces concurrent kernel executions to be serialized when a CUDA application is run with nvprof. 3.2.3. Profiling Scope When collecting events/metrics, nvprof profiles all kernels launched on all visible CUDA devices by default. This profiling scope can be limited by the following options. --devices <device IDs> applies to --events, --metrics, --query-events and --query-metrics options that follows it. It limits these options to collect events/ metrics only on the devices specified by <device IDs>, which can be a list of device ID numbers separated by comma. --kernels <kernel filter> applies to --events and --metrics options that follows it. It limits these options to collect events/metrics only on the kernels specified by <kernel filter>, which has the following syntax: <context id/name>:<stream id/name>:<kernel name>:<invocation> Each string in the angle brackets, except for invocation, can be a standard Perl regular expression. Empty string matches any number or character combination. Invocation should be a positive number, and indicates the nth invocation of the kernel. www.nvidia.com Profiler User's Guide DU-05982-001_v5.5 | 23