CPU Benchmark Performance: Simulation

Simulation and Science have a lot of overlap in the benchmarking world. The benchmarks that fall under Science have a distinct use for the data they output – in our Simulation section, these act more like synthetics but at some level are still trying to simulate a given environment.

In the encrypt/decrypt scenario, how data is transferred and by what mechanism is pertinent to on-the-fly encryption of sensitive data - a process by which more modern devices are leaning to for software security.

We are using DDR5 memory on the Ryzen 9 7950X3D and the other Ryzen 7000 series we've tested. This also includes Intel's 13th and 12th Gen processors. We tested the aforementioned platforms with the following settings:

  • DDR5-5600B CL46 - Intel 13th Gen
  • DDR5-5200 CL44 - Ryzen 7000
  • DDR5-4800 (B) CL40 - Intel 12th Gen

All other CPUs such as Ryzen 5000 and 3000 were tested at the relevant JEDEC settings as per the processor's individual memory support with DDR4.

Simulation

(3-1) Dwarf Fortress 0.44.12 World Gen 65x65, 250 Yr

(3-1b) Dwarf Fortress 0.44.12 World Gen 129x129, 550 Yr

(3-1c) Dwarf Fortress 0.44.12 World Gen 257x257, 550 Yr

(3-2) Dolphin 5.0 Render Test

(3-3) Factorio v1.1.26 Test, 10K Trains

(3-3b) Factorio v1.1.26 Test, 10K Belts

(3-3c) Factorio v1.1.26 Test, 20K Hybrid

(3-4) John The Ripper 1.9.0: Blowfish

(3-4b) John The Ripper 1.9.0: MD5

Looking at the results of our simulation-based tests, the Ryzen 9 7950X3D once again performs respectably across these tests. We would have expected higher performance in our Factorio benchmark, as the Ryzen 7 5800X3D and its 3D V-Cache did yield some impressive gains. This is likely due to the AMD PPM Provisioning and 3D V-Cache driver opting for frequency over cache when running this benchmark. That does show a little bit of a pitfall here for AMD.

CPU Benchmark Performance: Science CPU Benchmark Performance: Rendering And Encoding
Comments Locked

122 Comments

View All Comments

  • Gavin Bonshor - Monday, February 27, 2023 - link

    I'm currently in the middle of testing data in all three modes (Auto, Cache, and Frequency mode)
  • Dante Verizon - Monday, February 27, 2023 - link

    Radeon RX 6950 XT - There will be no significant differences using this GPU
  • Makaveli - Monday, February 27, 2023 - link

    The GPU is fine the bigger issue for me is those terrible memory speeds being used. Nobody buys jedec memory for their builds unless you are an OEM.
  • Ryan Smith - Monday, February 27, 2023 - link

    This discussion comes up now and then. But right now our stance remains unchanged: when AMD is willing to warranty memory overclocking, we'll start using it as a base setting.

    Otherwise, it's disingenuous to test a CPU in a state that's outside its normal operating parameters, and which would result in an RMA being rejected if anything happened to it.
  • Otritus - Monday, February 27, 2023 - link

    I think you should put this note inside the review and future reviews because it is a valid reason for why it is being benchmarked as such.
  • lopri - Wednesday, March 1, 2023 - link

    Agreed 100%
  • Oxford Guy - Wednesday, March 1, 2023 - link

    Has AMD or Intel ever denied a warranty claim because someone used an XMP profile?

    I'd love to see an article about that!
  • blkspade - Wednesday, March 22, 2023 - link

    Intel RMA survey actually asks if you used XMP as grounds to deny your RMA. They count it as oveclocking. AMD on the other hand doesn't even ask about memory profiles. I've had to do a RMA for both an i7 7700 and a R7 2700.
  • nandnandnand - Monday, February 27, 2023 - link

    Looks like a messy faceplant with the scheduler issues.
  • RHamel - Monday, February 27, 2023 - link

    Yes, the scheduler clearly isn't smart enough to assign threads to the optimal CCD with any consistency. AMD's "best of both worlds" design ends up being the worst of both worlds about half the time.

    They should have just put the 3D V-Cache on both CCDs and avoided this whole mess; anyone putting this (instead of a 7950X) in a workstation/HEDT obviously is running some kind of cache-limited workload and would prefer extra L3 on all cores to this design even if the scheduler worked perfectly.

Log in

Don't have an account? Sign up now