From 001afba76a110e08e836cdaefe7a1cc5c8db812d Mon Sep 17 00:00:00 2001 From: Peter Doak Date: Sat, 16 Jun 2018 18:48:08 -0400 Subject: [PATCH] improved readme --- examples/profiling/README.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/examples/profiling/README.md b/examples/profiling/README.md index bd532c615..130e84bac 100644 --- a/examples/profiling/README.md +++ b/examples/profiling/README.md @@ -7,7 +7,7 @@ With CUDA: * Running: With the performance tests set up. ``` shell [epd@oxygen ]$ export QMCPACK_APP=/path/to/your/instrumented/bin/qmcpack -[epd@oxygen ]$ cd /performace/NiO/sample/dmc-a4-e48-gpu +[epd@oxygen ]$ cd /your_scratch/performace/NiO/sample/dmc-a4-e48-gpu [epd@oxygen ]$ OMP_NUM_THREADS=12 XRAY_OPTIONS="patch_premain=true xray_mode=xray-basic" nvprof -o simul.nvprof $QMCPACK_APP NiO-fcc-S1-dmc.xml [epd@oxygen ]$ llvm-xray account xray-log.qmcpack.yrxHG1 -instr_map=$QMCPACK_APP -sort=med -top=10 -sortorder=dsc @@ -33,8 +33,17 @@ If you also have a new version of llvm installed you can use the newer xray tool Then convert into chrome viewable html doc using the [catapult](https://github.com/catapult-project/catapult) tool. -``` +``` shell ~/codes/catapult/tracing/bin/trace2html dmc-a4-e48-gpu.trace -o dmc-a4-e48-gpu.html ``` [example -- only works with chrome](http://cdash-minimal.ornl.gov/profiling/dmc-a4-e48-gpu.html) + +You can then download the nvprof trace: +``` shell +$ scp /your_scratch/performace/NiO/sample/dmc-a4-e48-gpu/simul.nvprof ./ +$ nvvp +``` +You'll need to import simul.nvprof to a new session in nvvp. +Then you'll be able look at the traces from the CPU and GPU point of view at the same time. +