DDR3-1333 Speed and Latency Shootout

Lowest Latency Test Results

Using a relatively safe 1.80 volt setting, the DDR3-1333 test modules reached the following "best stable timings" at 1600 MHz, 1333 MHz and 1066 MHz data rates.

Swipe to scroll horizontally
Lowest Stable Latencies at 1.80 Volts
Row 0 - Cell 0 DDR3-1600DDR3-1333DDR3-1066Rated Settings
Aeneon X-Tune DDR3-13339-8-8-158-7-6-136-5-5-108-8-8-15
G.Skill PC3-10600Failed8-7-7-147-6-6-129-9-9-24
Kingston HyperX PC3-11000Failed7-7-6-136-6-5-128-8-8-24
Kingston ValueRAM PC3-106009-7-6-158-6-6-126-5-4-98-8-8-24
Mushkin EM3-106669-8-7-148-6-5-146-5-4-149-9-9-24
OCZ Platinum PC3-106668-7-6-156-5-4-124-4-3-97-7-7-20
OCZ ReaperX PC3-106668-7-6-136-5-4-125-4-3-86-5-5-18
Patriot PC3-10666Unstable6-6-5-125-5-4-97-7-7-20
Super Talent PC3-106007-6-6-136-5-5-105-4-4-98-8-8-18
Wintec AMPX PC3-106008-7-6-156-5-4-125-4-3-99-9-9-24

OCZ pulls amazing 4-4-3-9 timings at a 1066 MHz data rate, while the potentially lower-cost Wintec AMPX finds itself in a three-way tie with both OCZ kits at DDR3-1333. Overclockers looking for the lowest latency might prefer Super Talent's 7-6-6-13 timings at a 1600 MHz data rate.

Patriots DDR3-1333 had reached a stable 1652 MHz data rate on Gigabyte's top-end P35 motherboard, but the Asus Maximus Extreme's X38 chipset appears to be just a little more finicky. The modules didn't even reach a 1600 MHz data rate on the newer platform, but tied for second place in DDR3-1333 latencies.

Lower latencies are meant to improve system performance, so let's consider what the benchmarks can tell us.

Thomas Soderstrom
Thomas Soderstrom is a Senior Staff Editor at Tom's Hardware US. He tests and reviews cases, cooling, memory and motherboards.
  • dv8silencer
    I have a question: on your page 3 where you discuss the memory myth you do some calculations:

    "Because cycle time is the inverse of clock speed (1/2 of DDR data rates), the DDR-333 reference clock cycled every six nanoseconds, DDR2-667 every three nanoseconds and DDR3-1333 every 1.5 nanoseconds. Latency is measured in clock cycles, and two 6ns cycles occur in the same time as four 3ns cycles or eight 1.5ns cycles. If you still have your doubts, do the math!"

    Based off of the cycle-based latencies of the DDR-333 (CAS 2), DDR2-667 (CAS 4), and DDR3-1333 (CAS8), and their frequences, you come to the conclusion that each of the memory types will retrieve memory in the same amount of time. The higher CAS's are offset by the frequences of the higher technologies so that even though the DDR2 and DDR3 take more cycles, they also go through more cycles per unit time than DDR. How is it then, that DDR2 and DDR3 technologies are "better" and provide more bandwidth if they provide data in the same amount of time? I do not know much about the technical details of how RAM works, and I have always had this question in mind.
  • Latency = How fast you can get to the "goodies"
    Bandwidth = Rate at which you can get the "goodies"
  • So, I have OCZ memory I can run stable at
    7-7-6-24-2t at 1333Mhz or
    9-9-9-24-2t at 1600Mhz
    This is FSB at 1600Mhz unlinked. Is there a method to calculate the best setting without running hours of benchmarks?
  • Sorry dude but you are underestimating the ReapearX modules,
    however hard I want to see what temperatures were other modules at
    a voltage of ~ 2.1v, does not mean that the platinum series is not performant but I saw a ReapearX which tended easy to 1.9v(EVP)940Mhz, that means nearly a DDR 1900, which is something, but in chapter of stability/temperature in hours of functioning, ReapearX beats them all.
  • All SDRAM (including DDR variants) works more or less the same, they are divided in banks, banks are divided in rows, and rows contain the data (as columns).
    First you issue a command to open a row (this is your latency), then in a row you can access any data you want at the rate of 1 datum per cycle with latency depending on pipelining.

    So for instance if you want to read 1 datum at address 0 it will take your CAS lat + 1 cycle.

    So for instance if you want to read 8 datums at address 0 it will take your CAS lat + 8 cycle.

    Since CPUs like to fill their cache lines with the next data that will probably be accessed they always read more than what you wanted anyway, so the extra throughput provided by higher clock speed helps.

    But if the CPU stalls waiting for RAM it is the latency that matters.
  • what is on pc3-10600s "s" ?