... | @@ -53,6 +53,10 @@ At the moment the majority of the time spent in our code is on waiting for stuff |
... | @@ -53,6 +53,10 @@ At the moment the majority of the time spent in our code is on waiting for stuff |
|
|
|
|
|
To analyse the data on your local machine you can use either [this nvidia tool](https://github.com/NVIDIA/cuda-profiler/tree/master/one_hop_profiling) to do things in real-time or (probably preferrably) you can just generate some stuff on Piz Daint with ```nvprof``` and copy this to your local machine.
|
|
To analyse the data on your local machine you can use either [this nvidia tool](https://github.com/NVIDIA/cuda-profiler/tree/master/one_hop_profiling) to do things in real-time or (probably preferrably) you can just generate some stuff on Piz Daint with ```nvprof``` and copy this to your local machine.
|
|
|
|
|
|
|
|
## API
|
|
|
|
|
|
|
|
https://devblogs.nvidia.com/parallelforall/cuda-pro-tip-generate-custom-application-profile-timelines-nvtx/
|
|
|
|
|
|
### Testing a single task
|
|
### Testing a single task
|
|
|
|
|
|
On branch cuda_test, you can edit and compile a test running a single task. To do so, copy the task that you wish to test in the tests/testcuda.cu file and update do_test_pair or do_test. You will also need to switch runPair on or off in the main. To compile the script, do (script written for daint)
|
|
On branch cuda_test, you can edit and compile a test running a single task. To do so, copy the task that you wish to test in the tests/testcuda.cu file and update do_test_pair or do_test. You will also need to switch runPair on or off in the main. To compile the script, do (script written for daint)
|
... | | ... | |