diff options
| author | Araq <rumpf_a@web.de> | 2012-09-17 00:31:41 +0200 |
|---|---|---|
| committer | Araq <rumpf_a@web.de> | 2012-09-17 00:31:41 +0200 |
| commit | 75abf7250325d90a74189ea7e4852d36c3fdd67c (patch) | |
| tree | 8f58e79a9330420722f6712fb27eeae59ef4fc4b /doc | |
| parent | ad6ee9e85723a742fe76e6903a63f2796136fe98 (diff) | |
| download | Nim-75abf7250325d90a74189ea7e4852d36c3fdd67c.tar.gz | |
profiler improvements
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/estp.txt | 5 |
1 files changed, 2 insertions, 3 deletions
diff --git a/doc/estp.txt b/doc/estp.txt index a3cbee516..48df19739 100644 --- a/doc/estp.txt +++ b/doc/estp.txt @@ -21,8 +21,7 @@ your own profiler. The setting ``--profiler:on`` defines the conditional symbol ``profiler``. After your program has finished the profiler will create a -file ``profile_resultsX.txt``(where ``X`` is a previously unused number) -containing the profiling results. +file ``profile_results.txt`` containing the profiling results. Since the profiler works by examining stack traces, it's essential that the option ``--stackTrace:on`` is active! Unfortunately this means that a @@ -35,7 +34,7 @@ Example results file The results file lists stack traces ordered by significance. The following example file has been generated by profiling the Nimrod compiler -itself: It shows that in total 4.1% of the runtime has been spent +itself: It shows that in total 5.4% of the runtime has been spent in ``crcFromRope`` or its children. In general the stack traces show you immediately where the problem is because |