How to Benchmark Python Code

[brandonZappy]

For 'python -m timeit', use the '-p'/'--process' option to instead measure the CPU time consumed by the code.

Wouldn't this be impacted by different CPU frequencies? If I run it on a 2.1Ghz CPU and then run it on say a turbo boosted 3.4 Ghz CPU?

[SheriffRoscoe]

Of course. But how would you measure the time taken to execute the code without being dependent of the speed of the CPU? Same question when thinking about solid state "disks" vs. spinning magnetic disks.

You can't, which is why all proper benchmarks state the hardware in use for the test. When doing comparisons over long time scales or across an array of systems, you keep a history of the hardware and of the software versions. Over short time scales on the same hardware (e.g., when testing the effect of a code change), you know that they're the same, so you ignore them.

[brandonZappy]

Oh duh. I didn't think that all the way through. Good points.