Ticket #9 (new enhancement)

Especially with code that takes a long time to execute (especially after the settrace call...) I would like to collect *all* calls for later offline investigation. I would suggest a save_graph and a load_graph? I can then save_graph (instead of save_dot, e.g.), then at a later time, load_graph, followed by save_dot (or make_dot_graph). That is the first step, the second is to allow filtering of this already-collected graph, so I can run the trace once, then generate graphs for various modules independently.

This might get clunky if one just adds bits and pieces, a slight redesign might be sensible?

Is there any performance reasons to have filters where they currently are? If we add "offline filters", there'd be two different places to filter. I might propose removing the online filters? (Or keeping them for legacy/support, though, how many users does pycallgraph currently have?)

http://thinktoomuch.net/2007/06/06/python-call-graphs/