A Timely Re-Discovery

Most users have no need to worry about the internals of a computer: point, click, run, play games, and spend money if they want something faster. However one of the important features in a system relates to how they measure time. A modern system relies on a series of both hardware and software timers, both internal and external, in order to maintain a linear relation between requests, commands, execution, and interrupts.

The timers have different users, such as following instructions, maintaining video coherency, tracking real time, or managing the flow of data. Timers can (but not always) use external references to ensure their own consistency – damage, unexpected behavior, and even thermal environments can cause timers to lose their accuracy.

Timers are highly relevant for benchmarking. Most benchmark results are a measure of work performed per unit time, or in a given time. This means that both the numerator and the denominator need to be accurate: the system has to be able to measure what amount of work has been processed, and how long it took to do it in. Ideally there is no uncertainty in either of those values, giving an accurate result.

With the advent of Windows 8, between Intel and Microsoft, the way that the timers were used in the OS were changed. Windows 8 had the mantra that it had to ‘support all devices’, all the way from the high-cost systems down to the embedded platforms. Most of these platforms use what is called an RTC, a ‘real time clock’, to maintain the real-world time – this is typically a hardware circuit found in almost all devices that need to keep track of time and the processing of data. However, compared to previous versions of Windows, Microsoft changed the way it uses timers, such that it was compatible with systems that did not have a hardware-based RTC, such as low-cost and embedded devices. The RTC was an extra cost that could be saved if the software was built to do so.

Ultimately, any benchmark software in play has to probe the OS to determine the current time during the benchmark to then at the end give an accurate result. However the concept of time, without an external verifying source, is an arbitrarily defined constant – without external synchronization, there is no guarantee that ‘one second’ on the system equals ‘one second’ in the real world. For the most part, all of us rely on the reporting from the OS and the hardware that this equality is true, and there are a lot of hardware/software engineers ensuring that this is the case.

However, back in 2013, it was discovered that it was fairly easy to 'distort time' on a Windows 8 machine. After loading into the operating system, any adjustment in the base frequency of the processor, which is usually 100 MHz, can cause the ‘system time’ to desynchronise with ‘real time’. This was a serious issue in the extreme overclocking community, where world records require the best system tuning: when comparing two systems at the same frequency but with different base clock adjustments, up to a 7% difference in results were observed when there should have been a sub-1% difference. This was down to how Windows was managing its timers, and was observed on most modern systems.

For home users, most would suspect that this is not an issue. Most users tend not to adjust the base frequencies of their systems manually. For the most part that is true. However, as shown in some of our motherboard testing over the years, frequency response due to default BIOS settings can provide an observable clock drift around a specified value, something which can be exacerbated by the thermal performance. Having a system with observable clock drift, and subsequent timing drift, is not a good thing. It relies on the accuracy and quality of the motherboard components, as well as the state of the firmware. This issue has formally been classified as ‘RTC Bias’.

The extreme overclocking community, after analysing the issue, found a solution: forcing the High Performance Event Timer, known as HPET, found in the chipset. Some of our readers will have heard of HPET before, however our analysis is more interesting than it first appears.

Why A PC Has Multiple Timers

Aside from the RTC, a modern system makes use of many timers. All modern x86 processors have a Time Stamp Counter (TSC) for example, that counts the number of cycles from a given core, which was seen back in the day as a high-resolution, low-overhead way to get CPU timing information. There is also a Query Performance Counter (QPC), a Windows implementation that relies on the processor performance metrics to get a better resolution version of the TSC, which was developed in the advent of multi-core systems where the TSC was not applicable. There is also a timer function provided by the Advanced Configuration and Power Interface (ACPI), which is typically used for power management (which means turbo related functionality). Legacy timing methodologies, such as the Programmable Interval Timer (PIT), are also in use on modern systems. Along with the High Performance Event Timer, depending on the system in play, these timers will run at different frequencies.

Ryzen 7 2700X with HPET Off
ASUS ROG Crosshair VII Hero

Core i7-8700K with HPET Off
ASRock Z370 Gaming i7

Core i7-6950X with HPET On
ASUS X99-E-10G

Core i7-6700K with HPET Off

Core i5-5200U with HPET Off

Core i7-3960X with HPET Off

The timers will be used for different parts of the system as described above. Generally, the high performance timers are the ones used for work that is more time sensitive, such as video streaming and playback. HPET, for example, was previously referred to by its old name, the Multimedia Timer. HPET is also the preferred timer for a number of monitoring and overclocking tools, which becomes important in a bit.

With the HPET timer being at least 10 MHz as per the specification, any code that requires it is likely to be more in sync with the real-world time (the ‘one-second in the machine’ actually equals ‘one-second in reality’) than using any other timer.

In a standard Windows installation, the operating system has access to all the timers available. The software used above is a custom tool developed to show if a system has any of those four timers (but the system can have more). For the most part, depending on the software instructions in play, the operating system will determine which timer is to be used – from a software perspective, it is fundamentally difficult to determine which timers will be available, so the software is often timer agnostic. There is not much of a way to force an algorithm to use one timer or another without invoking specific hardware or instructions that rely on a given timer, although the timers can be probed in software like the tool above.

HPET is slightly different, in that it can be forced to be the only timer. This is a two stage process:

The first stage is that it needs to be enabled in the BIOS. Depending on the motherboard and the chipset, there may or may not be an option for this. The options are usually for enable/disable, however this is not a simple on/off switch. When disabled, HPET is truly disabled. However, when enabled, this only means that the HPET is added to the pool of potential timers that the OS can use.

The second stage is in the operating system. In order to force HPET as the only timer to be used for the OS, it has to be explicitly mentioned in the system Boot Configuration Data (BCD). In standard operation, HPET is not in the BCD, so it remains in the pool of timers for the OS to use. However, for software to guarantee that the HPET is the only timer running, the software will typically request to make a change and make an accompanying system reboot to ensure the software works as planned. Ever wondered why some overclocking software requests a reboot *before* starting the overclock? One of the reasons is sometimes to force HPET to be enabled.

This leads to four potential configuration implementations:

  1. BIOS enabled, OS default: HPET is in list of potential timers
  2. BIOS enabled, OS forced: HPET is used in all situations
  3. BIOS disabled, OS default: HPET is not available
  4. BIOS disabled, OS forced: HPET is not available

Again, for extreme overclockers relying on benchmark results to be equal on Windows 8/10, HPET has to be forced to ensure benchmark consistency. Without it, the results are invalid.

The Effect of a High Performance Timer

With a high performance timer, the system is able to accurately determine clock speeds for monitoring software, or video streaming processing to ensure everything hits in the right order for audio and video. It can also come into play when gaming, especially when overclocking, ensuring data and frames are delivered in an orderly fashion, and has been shown to reduce stutter on overclocked systems. And perhaps most importantly, it avoids any timing issues caused by clock drift.

However, there are issues fundamental to the HPET design which means that it is not always the best timer to use. HPET is a continually upward counting timer, which relies on register recall or comparison metrics rather than a ‘set at x and count-down’ type of timer. The speed of the timer can, at times, cause a comparison to fail, depending on the time to write the compared value to the register and that time already passing. Using HPET for very granular timing requires a lot of register reads/writes, adding to the system load and power draw, and in a workload that requires explicit linearity, can actually introduce additional latency. Usually one of the biggest benefits to disabling HPET on some systems is the reduction in DPC Latency, for example.

An Audit after our Ryzen 2000-series Review AMD and Intel Have Different HPET Guidance
Comments Locked


View All Comments

  • bbertram - Thursday, April 26, 2018 - link

    I think you will see alot of websites testing these combinations and re-validating their results. How do we trust any benchmarks now? Going to be some fun reading in the coming weeks.
  • Ryan Smith - Thursday, April 26, 2018 - link

    "Please take this comment into account when deciding if you're going to be flipping HEPT switches with every game on both CPU brands."

    Thankfully, we have no need to flip any switches for HPET. The new testing protocol is that we're sticking with the default OS settings. Which means HPET is available to the OS, but the system isn't forced to use it over all other timers.

    "And hey, I didn't see it, but did you do any comparisons on if GPU maker makes a difference to the HEPT impact on CPU maker?" We've done a couple of tests internally. Right now it doesn't look like it makes a difference. Not that we'd expect it to. The impact of HPET is to the CPU.
  • HeyYou,It'sMe - Thursday, April 26, 2018 - link

    Even before the patches, using the HPET timer causes severe system overhead. This is a known issue that is exacerbated slightly by the patches, but there isn't a massive increase in overhead. AnandTech should post HPET overhead before and after the patches. You will find the impact is much the same.
  • eva02langley - Thursday, April 26, 2018 - link

    Also, HPET seems to have a higher impact on old games. Maybe it was the way older engine were developed.

    Also, are we sure HPET is not just messing with the FPS data since the timing could be off?
  • peevee - Thursday, April 26, 2018 - link

    Great illustration of the phrase that "it's better not to know than know something which isn't so".

    Standard 1kHz RTC is good enough for all real performance measurement where measured tasks run for at least a second or two (otherwise such performance just does not matter in the PC context). Multiple measurement, plus elimination of false precision from averaging the results would eliminate all errors significant for the task.

    When you have to change default system configuration to run the tests, the tests reflect these non-default configurations nobody is running at home or at work, and as such simply irrelevant.
  • pogostick - Thursday, April 26, 2018 - link

    I don't understand how using HPET on Intel could have such a drastic effect. Just the fact that it is available slows the system down? How? A benchmark only needs to access this timer once at the beginning and once at the end. There is no need for incessant polling of the clock. Is the only way to guarantee that you are using it to force it on for the whole system? What do these differences look like in other OSes? There are way too many questions unanswered here.

    Is it not more likely that using non-HPET timers allows the platform to essentially create it's own definition for what constitutes "1 second"? Wouldn't using a timer based on the core tend to stretch out the definition of "1 second" over a longer period if the core becomes heavily taxed or heated?

    These systems need to be tested with a common clock. Whether that is some specialized pcie device, or a network clock, or a new motherboard standard that offers special pins to an external clock source, or whatever, is to be determined elsewhere. All boards need to be using the same clock for testing.
  • Ryan Smith - Thursday, April 26, 2018 - link

    I don't understand how using HPET on Intel could have such a drastic effect. Just the fact that it is available slows the system down?

    It's not that it's available is the problem. The issue is that the OS is forced to use it for all timer calls.


    Relative to the other timers, such as QPC, HPET is a very, very expensive timer to check. It requires going to the OS kernel and the kernel in turn going to the chipset, which is quite slow and time-consuming compared to any other timer check.

    "A benchmark only needs to access this timer once at the beginning and once at the end. There is no need for incessant polling of the clock."

    Games have internal physics simulations and such. Which require a timer to see how much time has elapsed since the last step of the simulation. So the timer can actually end up being checked quite frequently.

    "Is the only way to guarantee that you are using it to force it on for the whole system?"

    As a user, generally speaking: yes. Otherwise a program will use the timer the developer has programmed it to use.

    "Wouldn't using a timer based on the core tend to stretch out the definition of "1 second" over a longer period if the core becomes heavily taxed or heated?"

    No. Modern Invariant timers are very good about keeping accurate time, and are very cheap to access.
  • pogostick - Friday, April 27, 2018 - link

    Thank you.
  • risa2000 - Monday, April 30, 2018 - link

    "Games have internal physics simulations and such. Which require a timer to see how much time has elapsed since the last step of the simulation. So the timer can actually end up being checked quite frequently."

    Would it be too difficult to set up a profiler session and count how many times is HPET called and eventually even from where?

    To produce such an impact it must be a load of calls and I still cannot imagine why so many.

    Next, why Intel suffers so much by forced HPET compared to new AMD?
  • Kaihekoa - Friday, April 27, 2018 - link

    Excuses excuses.

Log in

Don't have an account? Sign up now