3 ms·

There is no actual performance hit the number of frames per a given unit of real time is still identical the only thing that happens is that the frame counter o

There is no actual performance hit the number of frames per a given unit of real time is still identical the only thing that happens is that the frame counter on the machine does not count it accurately.

wtallis 9y ago
That may be true for some applications, but in general the FPS meter isn't the only thing that cares about wall time.
- dogma1138 9y ago
  Yes but were talking about this specific use case I'm not entirely sure if this actually would affect more significant things HPET was always PITA. I am wondering where did they get the Intel uses 24mhz timer from tho... hpet0: 4 comparators, 64-bit 14.318180 MHz counter
  - wtallis 9y ago
    On my Skylake system, I have: hpet0: 8 comparators, 64-bit 24.000000 MHz counter
    - dogma1138 9y ago
      I've tested on Broadwell/Haswell-E, KL and SKL-X I wonder wtf is going on. 24.0Mhz is also not an integer multiplier of the standard 8254/8253 PITs....
yardsale 9y ago
That's not true at all. HPET is very reliable and not prone to skewing at all. The problem is that accessing an HPET timestamp (via QPC in Windows) is very slow on certain Intel and AMD platforms. The HPET bug was already discovered last July, so Meltdown and Spectre have nothing to do with the bug but maybe adding performance penalties on top. Read this for details and try the timer benchmark in there: https://www.overclockers.at/articles/the-hpet-bug-what-it-is-and-what-it-isnt https://www.overclockers.at/articles/the-hpet-bug-what-it-is...