@@ -41,13 +41,13 @@ This file will open to the "Overview" section, which gives some overall data abo
41
41
the program ran, e.g., total run time, time spent doing garbage collection. One
42
42
important piece of information you'll get here is percentage of the total call
43
43
frames (i.e., blocks) that were interpreted (slowest, in red), L < speshed|/language/glossary#index-entry-Spesh > (faster,
44
- in orange), and JITted (fastest, in green).
44
+ in orange), and jitted (fastest, in green).
45
45
46
46
The next section, "Routines", is probably where you'll spend the most time. It has
47
47
a sortable and filterable table of routine (or block) name+file+line, the number of
48
48
times it ran, the inclusive time (time spent in that routine + time spent in all
49
49
routines called from it), exclusive time (just the time spent in that routine), and
50
- whether it was interpreted, speshed, or JITted (same color code as the "Overview"
50
+ whether it was interpreted, speshed, or jitted (same color code as the "Overview"
51
51
page). Sorting by exclusive time is a good way to know where to start optimizing.
52
52
Routines with a filename that starts like C < SETTING::src/core/ > or C < gen/moar/ > are
53
53
from the compiler, a good way to just see the stuff from your own code is to put
@@ -63,8 +63,8 @@ The "GC" section gives you detailed information about all the garbage collection
63
63
that occurred.
64
64
65
65
The "OSR / Deopt" section gives you information about On Stack Replacements (OSRs),
66
- which is when routines are "upgraded" from interpreted to speshed or JITted . Deopts
67
- are the opposite, when speshed or JITted code has to be "downgraded" to being
66
+ which is when routines are "upgraded" from interpreted to speshed or jitted . Deopts
67
+ are the opposite, when speshed or jitted code has to be "downgraded" to being
68
68
interpreted.
69
69
70
70
If the profile data is too big, it could take a long time for a browser to open
0 commit comments