21.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.

21.7.1 Effects of random sampling

21.7.2 Recursive functions

21.7.3 Structure accessors

21.7.4 Consequences of restricted profiling

21.7.5 Effect of compiler optimizations

21.7.6 Effect of compiler transforms

Common LispWorks User Guide (Macintosh version) - 21 Feb 2008