mirror of
https://github.com/nim-lang/Nim.git
synced 2026-06-07 12:24:19 +00:00
profiler improvements
This commit is contained in:
@@ -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
|
||||
|
||||
Reference in New Issue
Block a user