➜

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 Nitapol, lukasz.langa, miss-islington, ned.deily, rhettinger, ronaldoussoren, rvijayak, vstinner
Date 2019-08-27.06:39:36
SpamBayes Score -1.0
Marked as misclassified Yes
Message-id <1566887976.91.0.708058882501.issue36205@roundup.psfhosted.org>
In-reply-to
Content 
Oh, nicely spotted Rajiv Vijayakumar and thanks for the fix!


> instead of computing the total time as utime+stime, the code performs utime+utime, which explains the doubling observed.

Ooooooops, stupid me :-) I introduced the bug in:

commit c29b585fd4b5a91d17fc5dd41d86edff28a30da3
Author: Victor Stinner <victor.stinner@gmail.com>
Date:   Thu Nov 2 07:28:27 2017 -0700

    bpo-31784: Implement PEP 564: add time.time_ns() (#3989)

It seems like macOS was the most visible impacted platform. Windows and Linux has different implementations (GetProcessTimes and clock_gettime(CLOCK_PROCESS_CPUTIME_ID)).

Note: I wrote an article about time.perf_counter_ns() added in Python 3.7 (perf_counter, not process_time):
https://vstinner.github.io/python37-perf-counter-nanoseconds.html
History
Date User Action Args
2019-08-27 06:39:36vstinnersetrecipients: + vstinner, rhettinger, ronaldoussoren, ned.deily, lukasz.langa, miss-islington, rvijayak, Nitapol
2019-08-27 06:39:36vstinnersetmessageid: <1566887976.91.0.708058882501.issue36205@roundup.psfhosted.org>
2019-08-27 06:39:36vstinnerlinkissue36205 messages
2019-08-27 06:39:36vstinnercreate