➜

This issue tracker has been migrated to GitHub, and is currently read-only.
For more information, see the GitHub FAQs in the Python's Developer Guide.

Author vstinner
Recipients Red Glyph, eryksun, paul.moore, steve.dower, tim.golden, vstinner, zach.ware
Date 2019-08-14.21:49:29
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1565819369.87.0.549642834661.issue37859@roundup.psfhosted.org>
In-reply-to
Content 
> Process times [1] are stored as a 64-bit integer in units of 100 ns (1e-7). But the kernel schedules threads based on a timer that ticks every 15.625 ms by default. It can be lowered to about 0.5 ms, but this degrades battery life.

Patches are welcome to enhance time.get_clock_info() :-)

Don't rely too much on time.get_clock_info() on Linux neither: it basically always say 1 ns, even if the effective resolution is way worse.

See the PEP 418 for some numbers:
https://www.python.org/dev/peps/pep-0418/#process-time

I wrote these programs to write this PEP ;-)

https://github.com/python/peps/tree/master/pep-0418
History
Date User Action Args
2019-08-14 21:49:29vstinnersetrecipients: + vstinner, paul.moore, tim.golden, zach.ware, eryksun, steve.dower, Red Glyph
2019-08-14 21:49:29vstinnersetmessageid: <1565819369.87.0.549642834661.issue37859@roundup.psfhosted.org>
2019-08-14 21:49:29vstinnerlinkissue37859 messages
2019-08-14 21:49:29vstinnercreate