| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
8.1.3 Usage
- Function: statprof-active?
Returns
#tifstatprof-starthas been called more times thanstatprof-stop,#fotherwise.
- Function: statprof-reset sample-seconds sample-microseconds count-calls? . full-stacks?
Reset the statprof sampler interval to sample-seconds and sample-microseconds. If count-calls? is true, arrange to instrument procedure calls as well as collecting statistical profiling data. If full-stacks? is true, collect all sampled stacks into a list for later analysis.
Enables traps and debugging as necessary.
- Function: statprof-fold-call-data proc init
Fold proc over the call-data accumulated by statprof. Cannot be called while statprof is active. proc should take two arguments,
(call-data prior-result).Note that a given proc-name may appear multiple times, but if it does, it represents different functions with the same name.
- Function: statprof-proc-call-data proc
Returns the call-data associated with proc, or
#fif none is available.
- Function: statprof-display . _
Displays a gprof-like summary of the statistics collected. Unless an optional port argument is passed, uses the current output port.
- Function: statprof-display-anomolies
A sanity check that attempts to detect anomolies in statprof’s statistics.
- Function: statprof-fetch-stacks
Returns a list of stacks, as they were captured since the last call to
statprof-reset.Note that stacks are only collected if the full-stacks? argument to
statprof-resetis true.
- Function: statprof-fetch-call-tree
Return a call tree for the previous statprof run. The return value is a list of nodes, each of which is of the type: @@code node ::= (@@var@{proc@} @@var@{count@} . @@var@{nodes@}) @@end code
- Function: statprof thunk [#:loop] [#:hz] [#:count-calls?] [#:full-stacks?]
Profiles the execution of thunk.
The stack will be sampled hz times per second, and the thunk itself will be called loop times.
If count-calls? is true, all procedure calls will be recorded. This operation is somewhat expensive.
If full-stacks? is true, at each sample, statprof will store away the whole call tree, for later analysis. Use
statprof-fetch-stacksorstatprof-fetch-call-treeto retrieve the last-stored stacks.
- Special Form: with-statprof args
Profiles the expressions in its body.
Keyword arguments:
-
#:loop Execute the body loop number of times, or
#ffor no loopingdefault:
#f-
#:hz Sampling rate
default:
20-
#:count-calls? Whether to instrument each function call (expensive)
default:
#f-
#:full-stacks? Whether to collect away all sampled stacks into a list
default:
#f
-
| [ < ] | [ > ] | [ << ] | [ Up ] | [ >> ] | [Top] | [Contents] | [Index] | [ ? ] |
