How can you get the call tree with Python profilers?

Question:

I used to use a nice Apple profiler that is built into the System Monitor application. As long as your C++ code was compiled with debug information, you could sample your running application and it would print out an indented tree telling you what percent of the parent function’s time was spent in this function (and the body vs. other function calls).

For instance, if main called function_1 and function_2, function_2 calls function_3, and then main calls function_3:

main (100%, 1% in function body):
    function_1 (9%, 9% in function body):
    function_2 (90%, 85% in function body):
        function_3 (100%, 100% in function body)
    function_3 (1%, 1% in function body)

I would see this and think, “Something is taking a long time in the code in the body of function_2. If I want my program to be faster, that’s where I should start.”

How can I most easily get this exact profiling output for a Python program?

I’ve seen people say to do this:

import cProfile, pstats
prof = cProfile.Profile()
prof = prof.runctx("real_main(argv)", globals(), locals())
stats = pstats.Stats(prof)
stats.sort_stats("time")  # Or cumulative
stats.print_stats(80)  # 80 = how many to print

But it’s quite messy compared to that elegant call tree. Please let me know if you can easily do this, it would help quite a bit.

Asked By: user

||

Answers:

Check out this library http://pycallgraph.slowchop.com/ for call graphs. It works really well. If you want to profile specific functions, check out http://mg.pov.lt/blog/profiling.html

This is a result from the profilehooks module.

alt text

Answered By: Falmarri

I recently wanted the same thing, so I took a stab at implementing one myself.

The project’s on GitHub, https://github.com/joerick/pyinstrument

Here’s how you would use it:

from pyinstrument import Profiler

profiler = Profiler()
profiler.start()

# Code you want to profile

profiler.stop()

print(profiler.output_text())
Answered By: joerick

I just stumbled on this as well, and spent some time learning how to generate a call graph (the normal results of cProfile is not terribly informative). Future reference, here’s another way to generate a beautiful call-tree graphic with cProfile + gprof2dot + graphViz.

———————

  1. Install GraphViz: http://www.graphviz.org/Download_macos.php
  2. easy_install gprof2dot
  3. Run profile on the code.

    python -m cProfile -o myLog.profile <myScript.py> arg1 arg2 ...
    
  4. Run gprof2dot to convert the call profile into a dot file

    gprof2dot -f pstats myLog.profile -o callingGraph.dot
    
  5. Open with graphViz to visualize the graph

Here’s what the end result would look like!
Graph is color-coded- red means higher concentration of time.

Graph is color-coded- red means higher concentration of time

Answered By: Max Song

The gprof2dot approach extracts all information nicely, so I’m a fan. However, sometimes I want to look at timing data in a call tree, so I created tuna.

enter image description here

Install with

pip install tuna

and display your profile with

tuna program.prof
Answered By: Nico Schlömer
Categories: questions Tags: , ,
Answers are sorted by their score. The answer accepted by the question owner as the best is marked with
at the top-right corner.