Core 2 Duo: Effects Of Memory Timings

Written by Tim Smalley

July 18, 2006 // 4:18 p.m.

Tags: #2 #800 #allendale #conroe #core #corsair #crucial #ddr2 #duo #e6400 #e6600 #effects #evaluation #kingston #memory #mhz #ocz #performance #review #timings

Sisoft Sandra Memory Bandwidth & Latency:

Before we get on to our real-world benchmarking suite, we've run a couple of synthetic benchmarks to show the theoretical performance benefits of using tighter memory timings. The first thing we looked at was Sisoft Sandra 2007 memory performance - we used the Unbuffered Memory and Memory Latency tests to gauge theoretical memory performance.

Core 2 Duo: Effects Of Memory Timings Synthetic Benchmarks

Core 2 Duo: Effects Of Memory Timings Synthetic Benchmarks
As expected, we saw theoretical memory bandwidth improvements on both the E6600 and E6400 processors when tightening the memory timings. We also saw reductions in memory timings on both chips.

SuperPI Mod 1.5:

SuperPI Mod 1.5 is a popular benchmark among enthusiasts and the results are affected by memory bandwidth. You can download a copy of the application from

Core 2 Duo: Effects Of Memory Timings Synthetic Benchmarks
There were small improvements from running tighter memory timings in SuperPI too. The performance differences as a result of tightening memory timings were larger on the 2MB L2 cached Core 2 Duo E6400 processor - going from 4.0-4-4-12 to 3.0-3-3-9 improved the calculation time by almost one second.

On the other hand, the improvements between the same two memory settings was a mere half second on the Core 2 Duo E6600. This indicates that the Core 2 Duo E6600 doesn't suffer quite so much when tightening memory timings. That makes sense, considering that the E6600 utilises the larger 4MB L2 cache. Lets see if the same is true when using real applications.
Discuss this in the forums