VRMark, 3DMark & AotS: Escalation
VRMark & 3DMark
These are busy charts with the addition of our retested Intel platforms, including the Spectre Variant 2 microcode patches. At stock settings, the Ryzen 5 2600X outperforms its overclocked predecessor across the board, which is especially meaningful in the lightly-threaded VRMark workload. Overclocking yields significant gains in synthetic gaming benchmarks, which don't necessarily translate to the rest of our benchmark suite.
Several of the patched Intel processors do lose performance compared to before the updates. This is particularly apparent in VRMark on Intel's Core i7-8700K, while other tests reflect minimal regression. Meanwhile, the Core i5-8400 and -8600K give us mixed results. Core i7-7700K is a more representative measure of pre- and post-patch performance, and it takes a healthy dive in VRMark as well (verified several times by removing and reinstalling the OS-based Spectre patch).
Ashes of the Singularity: Escalation
Ryzen 5 2600X is clearly superior to its predecessor in threaded titles. After all, the stock 2600X beats an overclocked 1600X. Those gains propel the Ryzen 5 up the chart, where it matches a stock Core i7-8700K.
Flip over to the album's next slide, which includes Intel CPUs before and after we patched their platforms. The Core i7-7700K loses a few frames per second in our retest, falling outside of this consistent benchmark's margin of error. Aside from the Core i5-8400's gains, which remind us that firmware updates sometimes fine-tune performance, too, most of the Intel CPUs land within the run-to-run variance we expect to see.
MORE: Best CPUs
MORE: Intel & AMD Processor Hierarchy
MORE: All CPUs Content
Then there's the gaming suite chosen. Old Far Cry? The 5th is out. Where's AC: Origins, notoriously CPU hungry? Overwatch? FFXV?
Hell, even the older Deus Ex or Kingdom Come: Deliverance would have made more sense to test CPUs.
But yes, this shows that for anything below 1080ti, you're good with pretty much all of these CPUs. Yet it doesn't tell the whole story, and soon a new GPU generation will be released, probably introducing many here to GTX 1080ti levels of performance, so testing with it does make sense.
HPET has been disabled by default in Windows for a decade or so now. The OS can call on HPET if it needs it. The performance overhead of HPET is a known quantity, which is why the OS doesn't use it if possible.
We test without HPET disabled, which is enforced by our test scripts to ensure it stays that way.
Considering Anandtech got caught by the HPET bug and you never see it mentioned in any reviews until now. So now i question each review I have seen and will see unless in mentioned. The credibility of all benchmarks are in question unless it clear HPET is disabled. Good thing you script handles that, thank you for let me know.
Keep on providing great content, I've loved Tom's reviews for a LONG time.
No one mentions HPET because it is disabled by default in the OS. If we listed every single feature that we leave alone and do not alter...that would be a long list :)