[issue19007] precise time.time() under Windows 8: use GetSystemTimePreciseAsFileTime

Eryk Sun added the comment: > What are the expected benefits from changing? Just a higher > resolution? I'm not sure that's worth anything if it's inaccurate. GetSystemTimePreciseAsFileTime() returns an accurate timestamp, which is the current system time plus the difference between the curr

[issue19007] precise time.time() under Windows 8: use GetSystemTimePreciseAsFileTime

Steve Dower added the comment: What are the expected benefits from changing? Just a higher resolution? I'm not sure that's worth anything if it's inaccurate. -- ___ Python tracker _

[issue19007] precise time.time() under Windows 8: use GetSystemTimePreciseAsFileTime

STINNER Victor added the comment: Note: GetSystemTimePreciseAsFileTime() is restricted to desktop applications. The windowstimestamp.com has a warning on this function: http://www.windowstimestamp.com/description """ 2.1.4.2. Desktop Applications: GetSystemTimePreciseAsFileTime() (...) The f

[issue19007] precise time.time() under Windows 8: use GetSystemTimePreciseAsFileTime

STINNER Victor added the comment: Good news! I got a new fresh Windows 8.1 VM with Visual Studio 2015. I'm now able to work on this issue. I wrote a patch: time_precise.patch. Resolution computed in Python by https://hg.python.org/peps/file/tip/pep-0418/clock_resolution.py: GetSystemTimePrec

[issue19007] precise time.time() under Windows 8: use GetSystemTimePreciseAsFileTime

STINNER Victor added the comment: Python 3.5 has a new C function _PyTime_GetSystemClock() which uses the new _PyTime_t type. It now has a resolution of 1 nanosecond. Sorry, I don't have Windows 8 at home, so I cannot work on this issue. I guess that we should check at runtime if GetSystemTime

[issue19007] precise time.time() under Windows 8: use GetSystemTimePreciseAsFileTime

Changes by Akira Li <4kir4...@gmail.com>: -- nosy: +akira ___ Python tracker ___ ___ Python-bugs-list mailing list Unsubscribe: https

[issue19007] precise time.time() under Windows 8: use GetSystemTimePreciseAsFileTime

Changes by STINNER Victor : -- title: precise time.time() under Windows 8 -> precise time.time() under Windows 8: use GetSystemTimePreciseAsFileTime ___ Python tracker ___ _

[issue19007] precise time.time() under Windows 8

STINNER Victor added the comment: My patch for the issue #22043 replaces the _PyTime_timeval structure (10^-6 second resolution, 1 us) with a _PyTime_timespec structure (10^-9 second resolution, 1 ns). It may help for this issue. -- ___ Python track

[issue19007] precise time.time() under Windows 8

Changes by Mark Lawrence : -- nosy: +steve.dower, tim.golden, zach.ware versions: +Python 3.5 -Python 3.4 ___ Python tracker ___ ___ P

[issue19007] precise time.time() under Windows 8

New submission from Antoine Pitrou: For whoever is interested: Windows 8 apparently has a new API named GetSystemTimePreciseAsFileTime which returns the system API with a much better resolution than GetSystemTimeAsFileTime does ("The GetSystemTimePreciseAsFileTime function retrieves the curren

[issue19007] precise time.time() under Windows 8

Antoine Pitrou added the comment: "GetSystemTimePreciseAsFileTime() has very little overhead; the new function is even a little faster than GetSystemTimeAsFileTime(), a call takes a few ten nanoseconds." from http://www.windowstimestamp.com/description#C_2 --

[issue19007] precise time.time() under Windows 8

STINNER Victor added the comment: time.time() is sometimes used in performance critical code. Is GetSystemTimePreciseAsFileTime() as fast as GetSystemTimeAsFileTime()? Linux has the opposite: CLOCK_REALTIME_COARSE. This clock is less accurate but may be faster. http://lwn.net/Articles/342018/