AMD Ryzen 5 2600X Review: Spectre Patches Weigh In

By Paul Alcorn
published

Why you can trust Tom's Hardware Our expert reviewers spend hours testing and comparing products and services so you can choose the best for you. Find out more about how we test.

Rendering, Encoding & Compression

Rendering

Image 1 of 9

Threaded rendering workloads favor Ryzen's SMT-enabled cores. Ryzen 5 2600X slots in right where we'd expect it to land, while Intel's processors suffer slight performance hits after installing the Spectre mitigation patches. 

Encoding & Compression

Image 1 of 7

LAME is the quintessential example of a single-threaded workload, normally favoring Intel's per-core performance advantage. AMD's 2000-series Ryzen CPUs go a long way in closing the gap by offering better per-core performance than their predecessors.

Our threaded compression and decompression tests adsorb data directly from system memory, removing storage from the equation. The Ryzen 5 2600X fares well during the test, easily beating Intel's Core i5-8400 and -8600K. Given Windows' new dual page table addressing structure that prevents Meltdown-based attacks, we expected more performance overhead after the patches. However, the company's latest processors have a PCID (Post-Context Identifiers) feature that accelerates page table translations. As a result, older Core CPUs without the PCID feature are likely affected more than the ones we're testing. 

There's a larger delta between Intel and AMD processors during our HandBrake x265 test compared to the x264 benchmark due to its heavier distribution of AVX instructions. The 2600X slots in where we'd expect given its six cores with SMT technology.


MORE: Best CPUs


MORE: Intel & AMD Processor Hierarchy


MORE: All CPUs Content

Paul Alcorn
Paul Alcorn
Deputy Managing Editor

Paul Alcorn is the Deputy Managing Editor for Tom's Hardware US. He writes news and reviews on CPUs, storage and enterprise hardware.

42 Comments Comment from the forums
  • bbertram99
    HPET.....
    Reply
  • nitrium
    20922954 said:
    HPET.....
    ??? Yes it destroys Intel's performance (not AMD's), but it's off by default in Windows and there is no reason to force it on.
    Reply
  • bbertram99
    i was wondering if reviews will now be posting if they checked if it was on or not. I think they should since we don't always know when it being forced. Its not evident until you look. If they don't state its not forced on then we are left wondering.
    Reply
  • toyo
    What's the point of this? Where's the GTX 1080ti? The 1080 simply result in every CPU being able to feed it enough data so scores are almost similar. Hence anomalies like having the 8400 or 8600k often being better than the 8700K, which should be impossible considering the higher clocks. I mean, this CPU performed the best for 3-4 months, even after Meltdown/Spectre patches/BIOS, and now it suddenly has issues competing with its own family of CPUs that are half that price, really?
    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.
    Reply
  • PaulAlcorn
    20923085 said:
    i was wondering if reviews will now be posting if they checked if it was on or not. I think they should since we don't always know when it being forced. Its not evident until you look. If they don't state its not forced on then we are left wondering.

    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.
    Reply
  • nitrium
    20923162 said:
    Yet it doesn't tell the whole story, and soon a new GPU generation will be released, probably introducing many here to GTS 1080ti levels of performance, so testing with it does make sense.
    Agreed. I'm still using an i5 760 (@.3.4GHz) which was released in July 2010. I have had multiple GPU upgrades over the years (as of this moment I'm on an R9 390), so I also would very much like to know if a new CPU is as "future proof" as possible with regards to GPU upgrades.
    Reply
  • kilgor98
    Would the 8700k cost what it does today without Ryzen? They would still be feeding us quad cores on the same 14nm process.
    Reply
  • bbertram99
    Don't see how to quote you PAULALCORN.

    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.
    Reply
  • btmedic04
    so can we expect updated benchmarks in the 2700x's review being that the results are skewed by the lack of specter patches on the intel processors?
    Reply
  • PaulAlcorn
    20923324 said:
    Don't see how to quote you PAULALCORN.

    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 :)
    Reply