On 7/31/07, Michael Droettboom <md...@st...> wrote: > Eric Firing wrote: > > I don't have a lot of experience with profiling... > Slightly OT, but I do have a recommendation for anyone doing Python > profiling. I don't usually get very excited about GUI tools, but > KCachegrind (Linux only) is very slick and works great with Python. > It's really handy to be able to "browse" the calltree interactively to > explore what's going on. > > The trick (which is very non-obvious from the documentation), is that > you use Python's 'hotspot' profiler, then convert that to 'calltree' > format using hotspot2calltree (included with KCachegrind), and then load > that with KCachegrind. > > Just my two cents for something you may want to try, Yup. The link I posted earlier is basically a little wrapper that does all that. I wrote it so you wouldn't have to think :) I keep it in my path and can profile any python script with kcachegrind just by running one command. And yes, kcachegrind rocks. I'm also very much a non-gui person, yet I've found it invaluable for doing really complex profiling of very large python codes. Cheers, f