jyapayne/Nim
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

profiler improvements

Browse source
This commit is contained in:
Araq 2012-09-17 00:31:41 +02:00
commit 75abf72503
8 changed files with 110 additions and 71 deletions
Download patch file Download diff file Expand all files Collapse all files

5
doc/estp.txt
View file

@ -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