Feb. 21, 2012
5:30 p.m.
On Tue, Feb 21, 2012 at 1:00 PM, Sümer Cip <sumerc@gmail.com> wrote:
Is there a reason behind the fact that the Python profilers work with Wall time by default? There are OS-dependent ways to get the CPU time of a thread, and giving that choice to the user _somehow_ ( to use wall vs cpu time) might be a good feature?
The original reason was that the Unix wall clock was more accurate than its CPU clock. If that's changed we should probably (perhaps in a platform-dependent way) change the default to the most accurate clock available. -- --Guido van Rossum (python.org/~guido)