New in version 2.2.
This module provides a nicer interface to the _hotshot C module. Hotshot is a replacement for the existing profile module. As it’s written mostly in C, it should result in a much smaller performance impact than the existing profile module.
Note
The hotshot module focuses on minimizing the overhead while profiling, at the expense of long data post-processing times. For common usage it is recommended to use cProfile instead. hotshot is not maintained and might be removed from the standard library in the future.
Changed in version 2.5: The results should be more meaningful than in the past: the timing core contained a critical bug.
Note
The hotshot profiler does not yet work well with threads. It is useful to use an unthreaded script to run the profiler over the code you’re interested in measuring if at all possible.
Profile objects have the following methods:
New in version 2.2.
This module loads hotshot profiling data into the standard pstats Stats objects.
See also
Note that this example runs the python “benchmark” pystones. It can take some time to run, and will produce large output files.
>>> import hotshot, hotshot.stats, test.pystone
>>> prof = hotshot.Profile("stones.prof")
>>> benchtime, stones = prof.runcall(test.pystone.pystones)
>>> prof.close()
>>> stats = hotshot.stats.load("stones.prof")
>>> stats.strip_dirs()
>>> stats.sort_stats('time', 'calls')
>>> stats.print_stats(20)
850004 function calls in 10.090 CPU seconds
Ordered by: internal time, call count
ncalls tottime percall cumtime percall filename:lineno(function)
1 3.295 3.295 10.090 10.090 pystone.py:79(Proc0)
150000 1.315 0.000 1.315 0.000 pystone.py:203(Proc7)
50000 1.313 0.000 1.463 0.000 pystone.py:229(Func2)
.
.
.