During the debriefing meeting it was felt that we should say a few words on profiling, shortly after the introduction on the first day.
The reason is that parallellisation should only be done after other options like optimizing single threaded code have been exhausted.
So perhaps just before memory profiling, it would be good to teach two ways of identifying bottlenecks.
During the debriefing meeting it was felt that we should say a few words on profiling, shortly after the introduction on the first day. The reason is that parallellisation should only be done after other options like optimizing single threaded code have been exhausted. So perhaps just before memory profiling, it would be good to teach two ways of identifying bottlenecks.
lprun
, the line profiler:and
prun
:Here is an article with extensive info.
Also, there is SO.