Translating to IPC: All This for 3%?

Contrary to popular belief, increasing IPC is difficult. Attempt to ensure that each execution port is fed every cycle requires having wide decoders, large out-of-order queues, fast caches, and the right execution port configuration. It might sound easy to pile it all on, however both physics and economics get in the way: the chip still has to be thermally efficient and it has to make money for the company. Every generational design update will go for what is called the ‘low-hanging fruit’: the identified changes that give the most gain for the smallest effort. Usually reducing cache latency is not always the easiest task, and for non-semiconductor engineers (myself included), it sounds like a lot of work for a small gain.

For our IPC testing, we use the following rules. Each CPU is allocated four cores, without extra threading, and power modes are disabled such that the cores run at a specific frequency only. The DRAM is set to what the processor supports, so in the case of the new CPUs, that is DDR4-2933, and the previous generation at DDR4-2666. I have recently seen threads which dispute if this is fair: this is an IPC test, not an instruction efficiency test. The DRAM official support is part of the hardware specifications, just as much as the size of the caches or the number of execution ports. Running the two CPUs at the same DRAM frequency gives an unfair advantage to one of them: either a bigger overclock/underclock, and deviates from the intended design.

So in our test, we take the new Ryzen 7 2700X, the first generation Ryzen 7 1800X, and the pre-Zen Bristol Ridge based A12-9800, which is based on the AM4 platform and uses DDR4. We set each processors at four cores, no multi-threading, and 3.0 GHz, then ran through some of our tests.

For this graph we have rooted the first generation Ryzen 7 1800X as our 100% marker, with the blue columns as the Ryzen 7 2700X. The problem with trying to identify a 3% IPC increase is that 3% could easily fall within the noise of a benchmark run: if the cache is not fully set before the run, it could encounter different performance. Shown above, a good number of tests fall in that +/- 2% range.

However, for compute heavy tasks, there are 3-4% benefits: Corona, LuxMark, CineBench and GeekBench are the ones here. We haven’t included the GeekBench sub-test results in the graph above, but most of those fall into the 2-5% category for gains.

If we take out Cinebench R15 nT result and the Geekbench memory tests, the average of all of the tests comes out to a +3.1% gain for the new Ryzen 2700X. That sounds bang on the money for what AMD stated it would do.

Cycling back to that Cinebench R15 nT result that showed a 22% gain. We also had some other IPC testing done at 3.0 GHz but with 8C/16T (which we couldn’t compare to Bristol Ridge), and a few other tests also showed 20%+ gains. This is probably a sign that AMD might have also adjusted how it manages its simultaneous multi-threading. This requires further testing.

AMD’s Overall 10% Increase

With some of the benefits of the 12LP manufacturing process, a few editors internally have questioned exactly why AMD hasn’t redesigned certain elements of the microarchitecture to take advantage. Ultimately it would appear that the ‘free’ frequency boost is worth just putting the same design in – as mentioned previously, the 12LP design is based on 14LPP with performance bump improvements. In the past it might not have been mentioned as a separate product line. So pushing through the same design is an easy win, allowing the teams to focus on the next major core redesign.

That all being said, AMD has previously already stated its intentions for the Zen+ core design – rolling back to CES at the beginning of the year, AMD stated that they wanted Zen+ and future products to go above and beyond the ‘industry standard’ of a 7-8% performance gain each year.

Clearly 3% IPC is not enough, so AMD is combining the performance gain with the +250 MHz increase, which is about another 6% peak frequency, with better turbo performance with Precision Boost 2 / XFR 2. This is about 10%, on paper at least. Benchmarks to follow.

Improvements to the Cache Hierarchy: Lower Latency = Higher IPC Precision Boost 2 and XFR2: Ensuring It Hertz More
Comments Locked

545 Comments

View All Comments

  • NWRMidnight - Sunday, April 22, 2018 - link

    Considering they already stated they would be publishing their findings this coming week, you are wrong about not being able to provide clarification. But it is taking time because they have to go thru and run various tests with various setting changes to determine what is influencing their numbers. This is beyond what just running tests and writing up a review is. People want to know how they got their numbers, even at stock, and defaults, they have to go thru and turn off or on bios settings, windows settings, etc to determine and be able to explain the impact on the results.

    This pretty much doubles if not triples the time it would to do just a simple review. And since Ian was up for 36 hours straight to get the first review out (partially because they had to scrap 36 hours of testing results and start over). So, he had to actually go home and get some sleep so he could tackle this task with an energized and clear mind.

    So, how about you learn some patience and realize that they will get the information to us, or would you rather have it all rushed without any real details? They also most likely have weekends off, so in reality, we should not expect anything until mid week this week.
  • John_M - Monday, April 23, 2018 - link

    "partially because they had to scrap 36 hours of testing results and start over"

    Where was this mentioned and explained, please?
  • NWRMidnight - Monday, April 23, 2018 - link

    talks about having to throw out some of the data, and the reason, at the bottom of this page of the review:

    https://www.anandtech.com/show/12625/amd-second-ge...

    Here is Ian's comment on twitter:

    https://twitter.com/IanCutress/status/987366840442...
  • John_M - Monday, April 23, 2018 - link

    Do you mean this:

    "However, this is just AMD’s standard PB2: disabling it will disable PB2. Initially we turned it off, thinking it was a motherboard manufacturer tool, only to throw away some testing because there is this odd disconnect between AMD’s engineers and AMD’s marketing."

    I didn't read the tweet so didn't make the connection.
  • RafaelHerschel - Monday, April 23, 2018 - link

    A publication should either stand by its tests or not. If AnandTech is unsure about their results, they should temporarily pull the benchmarks since they might be misleading or place a much larger disclaimer.
  • Ranger1065 - Monday, April 23, 2018 - link

    Great news about avoiding Anandtech in future Rafael. Please make sure you stick to your word.
  • RafaelHerschel - Monday, April 23, 2018 - link

    @Ranger1065 I'll see this one out, and yes, then I'm gone for good. I don't understand why you are happy about people not visiting this site anymore. I'm pretty sure that AnandTech can use all the traffic they can get.

    It's sad that a once leading publication doesn't seem to have a place in the market anymore.
  • mapesdhs - Monday, May 14, 2018 - link

    Perhaps we're just happy that people who think we live in a completely black & white world won't be hanging around. Nuance is dead in this SJW world.
  • ET - Sunday, April 22, 2018 - link

    The 2700 is quoted as $309 in all benchmarks. Should that be $299?
  • MDD1963 - Sunday, April 22, 2018 - link

    FFS, *please* tell me this (crappy 8700K results) is not a result of using bastardly patched Windows Enterprise for the gaming tests ...!(For all those folks at home benching games with Windows Enterprise...yeah, that happens :/ )

Log in

Don't have an account? Sign up now