AMD and Intel Have Different HPET Guidance

A standard modern machine, with a default BIOS and a fresh Windows operating system, will sit on the first situation in the table listed above: the BIOS has HPET enabled, however it is not explicitly forced in the operating system. If a user sets up their machine with no overclocking or monitoring software, which is the majority case, then this is the implementation you would expect for a desktop.

AMD

We reached out to AMD and Intel about their guidance on HPET, because in the past it has both been unclear as well as it has been changed. We also reached out to motherboard manufacturers for their input.

For those that remember the Ryzen 7 1000-series launch, about a year ago from now, one point that was lightly mentioned among the media was that in AMD’s press decks, it was recommended that for best performance, HPET should be disabled in the BIOS. Specifically it was stated that:

Make sure the system has Windows High Precision Event Timer (HPET) disabled. HPET can often be disabled in the BIOS. [T]his can improve performance by 5-8%.

The reasons at the time were unclear as to why, but it was a minor part in the big story of the Zen launch so it was not discussed in detail. However, by the Ryzen 5 1000-series launch, that suggestion was no longer part of the reviewer guide. By the time we hit the Ryzen-2000 series launched last week, the option to adjust HPET in the BIOS was not even in the motherboards we were testing. We cycled back to AMD about this, and they gave the following:

The short of it is that we resolved the issues that caused a performance difference between on/off. Now that there is no need to disable HPET, there is no need for a toggle [in the BIOS].

Interestingly enough, with our ASUS X470 motherboard, we did eventually find the setting for HPET – it was not in any of the drop down menus, but it could be found using their rather nice ‘search’ function. I probed ASUS about whether the option was enabled in the BIOS by default, given that these options were not immediately visible, and was told:

It's enabled and never disabled, since the OS will ignore it by default. But if you enable it, then the OS will use it – it’s always enabled, that way if its needed it is there, as there would be no point in pulling it otherwise.

So from an AMD/ASUS perspective, the BIOS is now going to always be enabled, and it needs to be forced in the OS to be used, however the previous guidance about disabling it in the BIOS has now gone, as AMD expects performance parity.

It is worth noting that AMD’s tool, Ryzen Master, requires a system restart when the user first loads it up. This is because Ryzen Master, the overclocking and monitoring tool, requires HPET to be forced in order to do what it needs to do. In fact, back at the Ryzen 7 launch in 2017, we were told:

AMD Ryzen Master’s accurate measurements present require HPET. Therefore it is important to disable HPET if you already installed and used Ryzen Master prior to game benchmarking.

Ultimately if any AMD user has Ryzen Master installed and has been run at any point, HPET is enabled, even if the software is not running or uninstalled. The only way to stop it being forced in the OS is with a command to chance the value in the BCD, as noted above.

For the Ryzen 2000-series launch last week, Ryzen Master still requires HPET to be enabled to run as intended. So with the new guidance that HPET should have minimal effect on benchmarks, the previous guidance no longer applies.

Ryzen Master is not the only piece of software that requires HPET to be forced in order to do what it needs to do. For any of our readers that have used overclocking software and tools before, or even monitoring tools such as fan speed adjusters – if those tools have requested a restart before being used properly, there is a good chance that in that reboot the command has been run to enable HPET. Unfortunately it is not easy to generate a list, as commands and methods may change from version to version, but it can apply to CPU and GPU overclocking.

Intel

The response we had from Intel was a little cryptic:

[The engineers recommend that] as far as benchmarking is concerned, it should not matter whether or not HPET is enabled or not. There may be some applications that may not function as advertised if HPET is disabled, so to be safe, keep it enabled, across all platforms. Whatever you decide, be consistent across platforms.

A cold reading of this reply would seem to suggest that Intel is recommended HPET to be forced and enabled, however my gut told me that Intel might have confused ‘on’ in the BIOS with ‘forced’ through the OS, and I have asked them to confirm.

Looking back at our coverage of Intel platforms overall, HPET has not been mentioned to any sizeable degree. I had two emails back in 2013 from a single motherboard manufacturer stating that disabling HPET in the BIOS can minimise DPC latency on their motherboard, however no comment was made about general performance. I cannot find anything explicitly from Intel though.

A Timely Re-Discovery Forcing HPET On, Plus Spectre and Meltdown Patches
Comments Locked

242 Comments

View All Comments

  • eva02langley - Thursday, April 26, 2018 - link

    They didn't got it wrong, they simply used default setting for default systems. Even Intel told them to leave HPET on.
  • eddman - Thursday, April 26, 2018 - link

    No, Ian was forcing HPET to be used in the benches. He didn't use the default state. Intel did not tell them to FORCE HPET to be used either.
  • peevee - Thursday, April 26, 2018 - link

    They did got it wrong. 100% their fault, with the stupid excuse that their background is in overclocking.
  • rocky12345 - Wednesday, April 25, 2018 - link

    Good to see things cleared up on this. My question is this I under stand that on the AMD's systems turn HPET to forced on from Ryzen Master needing it am I right on that. So that explains why it was turned on for the AMD systems but if it was not at default for the Intel systems as well how or what changed it to forced on the Intel systems? Was it changed in the Intel bios to enabled which then forced the OS to use the forced on option. My other concern is that if it eats away at so much performance why havn't Intel and AMD come up with better ways to deal with this issue or is it kinda like a newer problem because of Spectre/Meltdown patches and micro code updates on the Intel platform and HPET in forced mode kills performance because of that.
  • johnsmith222 - Wednesday, April 25, 2018 - link

    They've forced HPET on in benchmarks via script (as I understand from article) and for AMD it is irrelevant be it on or off (also explained in the article).
  • rocky12345 - Wednesday, April 25, 2018 - link

    So basically the moral of the story here is leave things as the hardware vendor intended or in default settings and everything should be fine. This does raise about a million more questions on how reviewers should or even need to change the way they setup the gear for reviewing etc etc. It also confirms well this and probably a lot of other variables in the hardware that can skew results one way or another it answers the question or at least part of it as to why the same hardware performs so differently from review to review. Just for the record I am not saying Anandtech in any way tried to skew the numbers in anyway I am very sure that is not the case here.
  • Maxiking - Wednesday, April 25, 2018 - link

    Well, if you have been enforcing HPET on for all those years, it pretty much means that all the tests on this site are not valid and not representative at all.

    HPET is widly known as the reason causing several perfomance issues /stuttering, fps drops on cpus with more cores/ but I never personally believed it because there was no benchmarks to support it only some geeks on forums posting their latency screens with HPET on/off and anecdotal evidence from the people who allegedly gained/lost fps by turning it on/off.

    The point is..The benchmarks here are not run on the same stick of RAMS /frequencies, timings/ but the highest official supported frequency is used to simulate what the platform is capable of.

    So why turning/enforcing something on by default if it could potentionally cause performance regression and makes your avg, min, max, 99th percentile absolutelly skewed?
  • peevee - Thursday, April 26, 2018 - link

    This!
  • mapesdhs - Sunday, May 6, 2018 - link

    This what? Lost me there.

    Btw, some older benchmarks don't work with HPET off (I think 3DMark Vantage is one of them).
  • lefenzy - Wednesday, April 25, 2018 - link

    I'm pretty confused. In these cases, it's the denominator (time) that's changing that affects the resultant performance assessment right? The raw performance (numerator) is unchanged.

    e.g. FPS = frames / time. Frames remain the same, but time is measured differently.

Log in

Don't have an account? Sign up now