A Closer Look at Latency and Scaling

As was explained in the Core 2 Duo launch review, Core 2 Duo has not physically added a memory controller on the processor. The memory controller is still part of the motherboard chipset that drives Core 2 Duo. Intel added features that perform intelligent look-aheads on the memory controller to behave like lower latency. As you saw on pages 2 and 3, ScienceMark 2.0 shows the "intelligent look-aheads" in Core 2 Duo to be extremely effective, with Core 2 Duo memory now exhibiting lower apparent latency than AM2. However, not all latency benchmarks show the same results. Everest from Lavalys shows latency improvements in the new CPU revisions, but it shows Latency more as we would expect in evaluating Conroe. For that reason, our detailed benchmarks for latency will use both Everest 1.51.195, which fully supports the Core 2 Duo processor, and ScienceMark 2.0.

Latency, or how fast memory is accessed, is not a static measurement. It varies with memory speed and generally improves (goes down) as memory speed increases. To better understand what is happening with memory accesses we first looked at Sciencemark 2.0 Latency on both AM2 and Conroe.


ScienceMark shows Conroe Latency with a 45ns to 61ns lead at DDR2-400. Latency continues to decrease as memory speed increases with Core 2 Duo, reaching a value of about 30ns at DDR2-1067. The Trend line for AM2 is steeper than Core 2 Duo, increasing at a rapid rate until latency is virtually the same at DDR2-800.

It is very interesting that ScienceMark shows lower latency on Core 2 Duo than AM2, since we all know the on-chip AM2 controller has to be faster. We thought perhaps it was because all of the tested memory accesses could be contained in the shared 4MB cache of Core 2 Duo, but Alex Goodrich,one of the authors of ScienceMark, states that Version 2 is designed to test up to 16MB of memory, forseeing the day of larger caches. In addition he states the Core 2 duo prefetcher is clever enough to pick up all the patterns ScienceMark uses to "fool" hardware prefetchers. ScienceMark plans a revision with an algoritm that is harder to fool, but Alex commented that Conroe fooling their benchmark was "in itself a great indicator of performance".


Everest uses a different algorithm for measuring Latency, and it shows the on-chip AM2 DDR2 controller in the lead at all memory speeds, with Latency almost the same at the Core 2 Duo memory speed range of DDR2-400 to DDR2-533. However, the Everest trend lines are similar to those in ScienceMark, in that AM2 latency improves at a steeper rate than Core 2 Duo as memory speed increases.

The point to the Latency discussion is that, as expected, AMD has much more opportunity for performance improvement with memory speed increases in AM2. Intel will eventually reach the point, if the lines were extended, where they would have to move to an on-chip memory controller to further improve latency. This is not to take anything away from Intel's intelligent design on Core 2 Duo. They have found a solution that fixes a performance issue without requiring an on-chip controller - for now.

Memory Test Configuration Memory Bandwidth and Scaling
Comments Locked

118 Comments

View All Comments

  • zsdersw - Tuesday, July 25, 2006 - link

    I care about people making blatantly false claims.
  • Wesley Fink - Tuesday, July 25, 2006 - link

    We used the SAME memory timings on both processors if they were available. For the DDR2-1067 and DDR2-800 they were exactly the same on both processors in all tests, which is why they were used for our 2.93GHz comparison. At DDR2-667 and below, the Core 2 Duo could support timings like 3-2-2, where AM2 only supports 3-3-3. This article was to evaluate memory performance, so we did everything possible to keep all variables the same.

    Memory timings were DDR2-400 - 3-2-2-5; 533 - 3-2-2-6; 667 - 3-2-3-7; 800 - 3-3-3-9; 1067 - 4-3-4-11; DDR2-1112 - 5-4-5-14.
  • duploxxx - Wednesday, July 26, 2006 - link

    well those cas settings were to be expected when you saw the memory performance chart.
    you just killed the performance after ddr2 800 cas4 is ok but the minor step you have from ddr 1067 to ddr 1112 and again 1 cas higher is the end of good performance. so the memory of the fx to get to 2.9 was? that explains probably the lower performance vs the linear performance increase in the memory.....
  • Bingo13 - Wednesday, July 26, 2006 - link

    quote:

    you just killed the performance after ddr2 800 cas4 is ok but the minor step you have from ddr 1067 to ddr 1112 and again 1 cas higher is the end of good performance.


    The timings utilized by AnandTech were about the best you will see with current DDR2 memory. They did not kill the performance, the memory capability is what limited the testing. Tell me, where can you buy DDR2 that will do 3-3-3-9 at 1067. This review was more than fair in the settings it utilized for the tests and it took $450 memory to do it.
  • duploxxx - Thursday, July 27, 2006 - link

    yes i know but you don't get my point...
    we know fx34 will be 3.0 so its stupid to try and get an fx at 2,93.
    run an fx at 3.0 (multiplier change) with the nice cas3-3-3 like you did and the performance will be way better. now you killed the performance (speedbump cpu and memory) by dropping the cas to 4
  • Wesley Fink - Wednesday, July 26, 2006 - link

    DDR2-800 was 3-3-3-9 2.2V. The FX at 2.93GHz was running DDR2-1067 at 4-3-4-11 2.2V.
  • Gary Key - Tuesday, July 25, 2006 - link

    We had a slight change in pages after the article went live. Page seven now represents stock memory performance on each platform with page eight now showing the overclocked FX62 (11x266, 2.93GHz) compared to the X6800 (11x266, 2.93GHz). A comparison that is quite revealing based upon numerous comments about what the expected results of running a high memory strap and low latency settings on the AM2 platform would even out the performance differences between the two platforms.
  • Wesley Fink - Tuesday, July 25, 2006 - link

    We were moving pages around as it posted. The page references should now be correct. The page that AMD fans will likely hate is now page 8.

Log in

Don't have an account? Sign up now