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

23.7.1 Effects of random sampling

23.7.2 Recursive functions

23.7.3 Structure accessors

23.7.4 Consequences of restricted profiling

23.7.5 Effect of compiler optimizations

23.7.6 Effect of compiler transforms

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