LispWorks IDE User Guide > 22 The Profiler


22.7 Profiling pitfalls

It is generally only worth profiling code which has been compiled. If you profile interpreted code, the interpreter itself is profiled, and this skews the results for the actual Lisp program.

Macros cannot be profiled because they are expanded during the compilation process.

22.7.1 Effects of random sampling

22.7.2 Recursive functions

22.7.3 Structure accessors

22.7.4 Consequences of restricted profiling

22.7.5 Effect of compiler optimizations

22.7.6 Effect of compiler transforms

LispWorks IDE User Guide (Macintosh version) - 22 Dec 2009