&gt; cProfile takes a while to learn how to use well.<p>I bet :) I have only scratched the surface, that&#x27;s for sure.<p>&gt; What didn&#x27;t you like about line_profiler?<p>In this case I was trying to profile the overall simulation codebase to find the slow spots (rather than guess) - a simulation that takes 60 minutes to run. line_profiler wasn&#x27;t great at giving digestible results from that - and I haven&#x27;t worked out how to write all output (across multiple modules) to file, without specifying the file in each decorator.<p>I&#x27;ve started to break the codebase down into &#x27;tests&#x27; to measure each algorithm separately, and will give line_profiler another go then.<p>Re memory_profiler, while the mprof command showed all peaks, the line by line output only showed the result after executing each line - so when 4GB of RAM disappeared in a skimage call, only to be released at the end - it wasn&#x27;t reflected in the output. Which is tricy when trying to reduce overall memory usage.