>
> 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.
>
>
Currently it seems clock_gettime() APIs have nanosecond resolution
On Tue, Feb 21, 2012 at 1:00 PM, Sümer Cip 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
Python 3.3 has two new functions in the time module: monotonic() and
wallclock().
Victor
___
Python-Dev mailing list
Python-Dev@python.org
http://mail.python.org/mailman/listinfo/python-dev
Unsubscribe:
http://mail.python.org/mailman/options/python-dev/
On Tue, Feb 21, 2012 at 2:00 PM, Sümer Cip wrote:
> Hi all,
>
> 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) mig
Hi all,
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?
--
Sumer Cip
__
