Thanks for the hint. I am currently happy with %prun followed by %lprun. The only thing I dislike about this is that I have to guess who calls the most offending method or function, but it's not much of a hassle, since %prun also includes the cumulative timings.
Martin Am Freitag, 15. September 2017 09:14:32 UTC+2 schrieb Maarten Derickx: > > By the way, if you are doing a lot of optimisation you should consider > using gprof2dot https://github.com/jrfonseca/gprof2dot . It can turn your > python profiling data into a really useful grafical visualisation of the > call graph, instantly showing you which parts of the code to optimize. And > I imagine in your case also showing you where the differences come from. -- You received this message because you are subscribed to the Google Groups "sage-devel" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-devel+unsubscr...@googlegroups.com. To post to this group, send email to sage-devel@googlegroups.com. Visit this group at https://groups.google.com/group/sage-devel. For more options, visit https://groups.google.com/d/optout.
