CPU Tests: Microbenchmarks

Core-to-Core Latency

As the core count of modern CPUs is growing, we are reaching a time when the time to access each core from a different core is no longer a constant. Even before the advent of heterogeneous SoC designs, processors built on large rings or meshes can have different latencies to access the nearest core compared to the furthest core. This rings true especially in multi-socket server environments.

But modern CPUs, even desktop and consumer CPUs, can have variable access latency to get to another core. For example, in the first generation Threadripper CPUs, we had four chips on the package, each with 8 threads, and each with a different core-to-core latency depending on if it was on-die or off-die. This gets more complex with products like Lakefield, which has two different communication buses depending on which core is talking to which.

If you are a regular reader of AnandTech’s CPU reviews, you will recognize our Core-to-Core latency test. It’s a great way to show exactly how groups of cores are laid out on the silicon. This is a custom in-house test built by Andrei, and we know there are competing tests out there, but we feel ours is the most accurate to how quick an access between two cores can happen.

AMD’s move from a dual 4-core CCX design to a single larger 8-core CCX is a key characteristic of the new Zen3 microarchitecture. Beyond aggregating the separate L3’s together for a large single pool in single-threaded scenarios, the new Cezanne-based mobile SoCs also completely do away with core-to-core communications across the SoC’s infinity fabric, as all the cores in the system are simply housed within the one shared L3.

What’s interesting to see here is also that the new monolithic latencies aren’t quite as flat as in the previous design, with core-pair latencies varying from 16.8ns to 21.3ns – probably due to the much larger L3 this generation and more wire latency to cross the CCX, as well as different boost frequencies between the cores. There has been talk as to the exact nature of the L3 slices, whether they are connected in a ring or in an all-to-all scenario. AMD says it is an 'effective' all-to-all, although the exact topology isn't quite. We have some form of mesh with links, beyond a simple ring, but not a complete all-to-all design. This will get more complex should AMD make these designs larger.

Cache-to-DRAM Latency

This is another in-house test built by Andrei, which showcases the access latency at all the points in the cache hierarchy for a single core. We start at 2 KiB, and probe the latency all the way through to 256 MB, which for most CPUs sits inside the DRAM (before you start saying 64-core TR has 256 MB of L3, it’s only 16 MB per core, so at 20 MB you are in DRAM).

Part of this test helps us understand the range of latencies for accessing a given level of cache, but also the transition between the cache levels gives insight into how different parts of the cache microarchitecture work, such as TLBs. As CPU microarchitects look at interesting and novel ways to design caches upon caches inside caches, this basic test proves to be very valuable.

As with the Ryzen 5000 Zen3 desktop parts, we’re seeing extremely large changes in the memory latency behaviour of the new Cezanne chip, with AMD changing almost everything about how the core works in its caches.

At the L1 and L2 regions, AMD has kept the cache sizes the same at respectively 32KB and 512KB, however depending on memory access pattern things are very different for the resulting latencies as the engineers are employing more aggressive adjacent cache line prefetchers as well as employing a brand-new cache line replacement policy.

In the L3 region from 512KB to 16 MB - well, the fact that we’re seeing this cache hierarchy quadrupled from the view of a single core is a major benefit of cache hit rates and will greatly benefit single-threaded performance. The actual latency in terms of clock cycles has gone up given the much larger cache structure, and AMD has also tweaked and changes the dynamic behaviour of the prefetchers in this region.

In the DRAM side of things, the most visible change is again this much more gradual latency curve, also a result of Zen3’s newer cache line replacement policy. All the systems tested here feature LPDDR4X-4266 memory, and although the new Cezanne platform has a slight advantage with the timings, it ends up around 13ns lower latency at the same 128MB test depth point into DRAM, beating the Renoir system and tying with Intel’s Tiger Lake system.

Frequency Ramping

Both AMD and Intel over the past few years have introduced features to their processors that speed up the time from when a CPU moves from idle into a high powered state. The effect of this means that users can get peak performance quicker, but the biggest knock-on effect for this is with battery life in mobile devices, especially if a system can turbo up quick and turbo down quick, ensuring that it stays in the lowest and most efficient power state for as long as possible.

Intel’s technology is called SpeedShift, although SpeedShift was not enabled until Skylake.

One of the issues though with this technology is that sometimes the adjustments in frequency can be so fast, software cannot detect them. If the frequency is changing on the order of microseconds, but your software is only probing frequency in milliseconds (or seconds), then quick changes will be missed. Not only that, as an observer probing the frequency, you could be affecting the actual turbo performance. When the CPU is changing frequency, it essentially has to pause all compute while it aligns the frequency rate of the whole core.

We wrote an extensive review analysis piece on this, called ‘Reaching for Turbo: Aligning Perception with AMD’s Frequency Metrics’, due to an issue where users were not observing the peak turbo speeds for AMD’s processors.

We got around the issue by making the frequency probing the workload causing the turbo. The software is able to detect frequency adjustments on a microsecond scale, so we can see how well a system can get to those boost frequencies. Our Frequency Ramp tool has already been in use in a number of reviews.

Our frequency ramp showcases that AMD does indeed ramp up from idle to a high speed within 2 milliseconds as per CPPC2. It does take another frame at 60 Hz (16 ms) to go up to the full turbo of the processor mind.

Ryzen 5000 Mobile: SoC Upgrades Power Consumption
POST A COMMENT

218 Comments

View All Comments

  • Stuka87 - Wednesday, January 27, 2021 - link

    Really no reason for them to move away from Vega for these chips. Do you also complain that Intel has not changed their IGP for years?

    The efficiency of Vega is quite good when not OC'ed way past where it should be like in the desktop cards. And it still offers adequate performance for the majority of people looking at a laptop. For anything more you want a discrete card anyway.
    Reply
  • Unashamed_unoriginal_username_x86 - Thursday, January 28, 2021 - link

    Just on the Intel point, it's worth noting that they've had to develop GPU IP specifically for their CPUs. The paradigm has changed with the advent of Xe scalable, but even then the first product released with Xe was a CPU. Obviously AMD is disadvantaged with RTG not being as tightly nit as Intel's GPU group Reply
  • IGTrading - Tuesday, January 26, 2021 - link

    Amazing execution from AMD.

    Unfortunately, the only way they could gain some significant market share would be if they manage to source enough capacity from TSMC.

    The demand for AMD CPUs in the market is huge.

    At Amazon, AMD's chips come with a +50% price premium on a regular basis. SONY & Microsoft are going nuts trying to get more chips from AMD.

    If AMD managed to negotiate well their cut from TSMC, we should see an explosion of AMD's revenue in 2021.

    The new crypto boom will only propel AMD's ASPs even higher, although it will annoy the IT enthusiasts.

    Great piece, Ian! Thanks.
    Reply
  • Deicidium369 - Wednesday, January 27, 2021 - link

    Not a question of capacity - it's the fact that TSMCs fragile long supply chain is broken and limited resources have to be allocated - and AMD is contractually obligated to reach delivery targets for the Console SOCs. They have to use the limited resources to provide the ultra high volume, ultra low margin SOCs over their high margin PC GPUs and CPUs.

    In this case, it's not AMD's fault - it's an issue with TSMC
    Reply
  • Spunjji - Thursday, January 28, 2021 - link

    "TSMCs fragile long supply chain is broken"
    ---citation needed---
    Reply
  • Qasar - Thursday, January 28, 2021 - link

    ---will never see it--- Reply
  • e36Jeff - Tuesday, January 26, 2021 - link

    Minor quibble, the chart at the bottom of the first page lists the Flow X13's memory speed as LPDDR4-3267 rather than 4267. Reply
  • Silma - Tuesday, January 26, 2021 - link

    It's one thing to develop great processors, it's entirely another thing to effectively ship them.
    I would have liked to purchase a Zen 3 processors for my new PC, but I had to make do with a 3700X.
    Would have been interested by an RTX 3070 or an AMD latest gen graphic card, but again, they only seem to exist in the hands of testers, YouTubers and twitchers.

    Let's see if AMD can really ship a decent number of Zen 3 mobile CPUs.
    Reply
  • bji - Tuesday, January 26, 2021 - link

    All your problems are easily solved. Just go to MicroCenter! Reply
  • Qasar - Tuesday, January 26, 2021 - link

    and if there is no microcenter near you, then what ? Reply

Log in

Don't have an account? Sign up now