Mention --num-callers more in DHAT docs.

diff --git a/dhat/docs/dh-manual.xml b/dhat/docs/dh-manual.xml
index 56f5b6aee59c9c32d51695f4197a3cdd74967463..da71720c33c54f025f956c8558a37e6b6a2e8878 100644 (file)
--- 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.</para>
 
 <para>Second, you need to run your program under DHAT to gather the profiling
-information.</para>
+information. You might need to reduce the <option>--num-callers</option> 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.</para>
 
 <para>Finally, you need to use DHAT's viewer (in a web browser) to get a
 detailed presentation of that information.</para>
@@ -146,6 +148,10 @@ built with full debugging information.</para>
 <computeroutput>dh_view.html</computeroutput>. Use the "Load" button to choose
 a DHAT output file to view.</para>
 
+<para>If loading takes a long time, it might be worth re-running DHAT with a
+smaller <option>--num-callers</option> value to reduce the stack depths,
+because this can significantly reduce the size of DHAT's output files.</para>
+
 
 <sect2><title>The Output Header</title>