All Manuals > LispWorks IDE User Guide > 24 The Profiler


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

24.7.1 Effects of random sampling

24.7.2 Recursive functions

24.7.3 Structure accessors

24.7.4 Consequences of restricted profiling

24.7.5 Effect of compiler optimizations

24.7.6 Effect of compiler transforms

LispWorks IDE User Guide (Windows version) - 25 Nov 2011