- From: Mark Rejhon <mark@blurbusters.com>
- Date: Thu, 22 Aug 2013 00:31:01 -0400
- To: public-web-perf@w3.org
- Message-ID: <CANDAP14TB5LnxMOrM-pHXgV1qc61krq8aG4ptSd92ExuQHqCzg@mail.gmail.com>
My TestUFO website just transmitted a AJAX web visitor log update with a * backwards-tick* in performance.now() .... This is a less-than-1-in-1000 occurence, I've reported it to the browser vendor ( https://bugzilla.mozilla.org/show_bug.cgi?id=908040 ) Some browsers are calling QueryPerformanceCounter() to calculate performance.now() values on Windows platforms. There is a known bug on some AMD CPU chipset drivers: http://stackoverflow.com/questions/644510/cpu-clock-frequency-and-thus-queryperformancecounter-wrong "QueryPerformanceCounter() and QueryPerformanceFrequency() offer a bit better resolution, but have different issues. For example in Windows XP, all AMD Athlon X2 dual core CPUs return the PC of either of the cores "randomly" (the PC sometimes jumps a bit backwards), unless you specially install AMD dual core driver package to fix the issue. We haven't noticed any other dual+ core CPUs having similar issues (p4 dual, p4 ht, core2 dual, core2 quad, phenom quad)." Microsoft also has a KB article about tick values jumping around too, as well: http://support.microsoft.com/kb/274323
Received on Thursday, 22 August 2013 04:31:28 UTC