NextPrevUpTopContentsIndex

12.4 Profiler output

A typical report would be:

profile-stacks called 564 times
 
Call tree
Symbol                seen   (%)
    1: MOD              17 (  3)
     2: FLOOR            5 (  1)
    1: EQL               8 (  1)
    1: >=                7 (  1)
     2: REALP            2 (  0)
    1: +                 6 (  1)
    1: LENGTH            4 (  1)
 
 
Cumulative profile summary
Symbol      called  profile   (%)      top   (%)
MOD        1000000       17 (  3)        8 (  1)
EQL        2000117        8 (  1)        8 (  1)
>=         1000001        7 (  1)        5 (  1)
+          1000000        6 (  1)        6 (  1)
FLOOR      1000000        5 (  1)        5 (  1)
LENGTH     2000086        4 (  1)        4 (  1)
REALP      1000001        2 (  0)        2 (  0)
 
Top of stack not monitored 93% of the time

The first line means that Lisp was interrupted 564 times by the profiler.

The call tree shows that in 17 of these interrupts (3% of them) the profiler found the function mod on the stack, in 5 of these interrupts it found the function floor on the stack, and so on. Moreover, floor only appears under the mod branch of the tree, which means that each of these times floor was called by mod .

The cumulative profile summary also shows how many times each symbol was found on the stack. Moreover it shows that the function mod was called 1000000 times, the function eql was called 2000117 times, and so on. In 17 of these interrupts it found the function mod on the stack, and on 8 of these occasions mod was on the top of the stack. You can deduce that 526 times the function on the top of the stack was none of those reported.

You can control sort order of the cumulative profile summary with print-profile-list .


LispWorks User Guide - 11 Mar 2008

NextPrevUpTopContentsIndex