From b71265fbc9e65936a46158ffb85a5242efbb741e Mon Sep 17 00:00:00 2001 From: Nicholas Nethercote Date: Mon, 8 Apr 2019 10:18:38 +1000 Subject: [PATCH] Mention --num-callers more in DHAT docs. --- dhat/docs/dh-manual.xml | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/dhat/docs/dh-manual.xml b/dhat/docs/dh-manual.xml index 56f5b6aee5..da71720c33 100644 --- a/dhat/docs/dh-manual.xml +++ b/dhat/docs/dh-manual.xml @@ -67,7 +67,9 @@ Valgrind use, you probably do want to turn optimisation on, since you should profile your program as it will be normally run. Second, you need to run your program under DHAT to gather the profiling -information. +information. You might need to reduce the value +to get reasonably-sized output files, especially if you are profiling a large +program; some trial and error might be needed to find a good value. Finally, you need to use DHAT's viewer (in a web browser) to get a detailed presentation of that information. @@ -146,6 +148,10 @@ built with full debugging information. dh_view.html. Use the "Load" button to choose a DHAT output file to view. +If loading takes a long time, it might be worth re-running DHAT with a +smaller value to reduce the stack depths, +because this can significantly reduce the size of DHAT's output files. + The Output Header -- 2.47.2