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

19.7.1 Effects of random sampling

19.7.2 Recursive functions

19.7.3 Structure accessors

19.7.4 Consequences of restricted profiling

19.7.5 Effect of compiler optimizations

19.7.6 Effect of compiler transforms

Common LispWorks User Guide (Macintosh version) - 11 Apr 2005