You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: org/implementation-details.org
+3-5Lines changed: 3 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -54,7 +54,7 @@ You can profile Clasp compiled code and C++ together. On linux we use the ~perf~
54
54
55
55
** Profiling on linux
56
56
57
-
Clasp generates just in time (JIT) code for which we need symbol information. Use the ~(ext:generate-perf-map)~ command within clasp to generate a ~/tmp/perf-<pid>.map file that ~perf~ will use to convert addresses to symbols. Do this just prior to evaluating the code that you want to profile so that you get the maximum coverage of JITted symbols.
57
+
Clasp generates just in time (JIT) code for which we need symbol information. Use the ~(ext:generate-perf-map)~ function within clasp to generate a ~/tmp/perf-<pid>.map~ file that ~perf~ will use to convert addresses to symbols. Do this just prior to evaluating the code that you want to profile so that you get the maximum coverage of JITted symbols.
In another window, within the FlameGraph directory do the following..
86
86
87
-
The ~perf~ profiling stack is only 127 frames deep by default and that is not enough for many profiling rungs. Use the following command to increase the depth.
0 commit comments