LINPACK Benchmark

At first I wasn't going to include the results of the LINPACK benchmark, but I figured there's no reason for them to go to waste as they were used for stability testing. The LINPACK benchmark is a measurement of a system's floating-point computing power. Today, it's widely used by enthusiasts for testing the stability of their overclocked systems. The later versions of LINPACK include support for Intel's AVX instruction set, which stress the CPU and RAM even more than before. We'll be using a front end to the LINPACK benchmark called LinX.

LinX v0.6.4 - Linpack Benchmark v10.3.4.007

Now we begin to see how that extra ~36% of bandwidth really affects system performance. As you can see, there's not exactly a ~36% advantage in LINPACK from the fastest to the slowest. Here, we're barely seeing a ~3% advantage for the faster memory. Once we get to DDR3-1600, there's not much of a difference at all.

PCMark 7

We'll measure overall system performance using the PCMark suite. This will perform a broad range of tests including video playback, video transcoding (downscaling), system storage (gaming), graphics (DX9), image manipulation, system storage (importing pictures), web browsing, data decrypting, and system storage (Windows Defender).

PCMark 7 v1.0.4 - PCMark Suite

If you take a step back and look at performance from an overall perspective, you can see that faster memory doesn't really have much of an effect. Every speed tested shows a ~2% performance increase over the slowest memory. Outside of CAS 9 DDR3-1333, then, you can pretty much use any DDR3 memory and get close to optimal performance in general applications.

AIDA64 Memory Benchmark 7-Zip, x264 Encoding, and Cinebench
Comments Locked

76 Comments

View All Comments

  • tomx78 - Tuesday, July 26, 2011 - link

    Article is called "choosing the best DDR3" so I agree they should test T1. Without it whole article is useless. It still does not answer question which DDR3 is best. If DDR3-2133 can't do T1 but DDR3-1600 can which one is faster?
  • Impulses - Monday, July 25, 2011 - link

    If you're pinching pennies and trying to build a system on a budget, even the $10 premium for anything but a basic 1333 kit doesn't seem worthwhile... I actually chose my last 2x4GB kit based on price and looks more than anything, heh, the old G.skill Sniper heatspreaders (the blue-ish version) matched my MSI mobo well and looked like they'd be the least likely to interfere with any heatsink. Some of the heatspreaders on pricier kits are crazy big, not to mention kinda gaudy.
  • Finally - Tuesday, July 26, 2011 - link

    Let me repeat: You buy your RAM based on... aesthetics?
    No further questions, thanks.
  • Finraziel - Wednesday, July 27, 2011 - link

    Well as this test showed, there is little performance gain to be had, so what else is there to base your choice on? Especially for people with windows it can be important. And if you buy really fast memory that wont fit under your heatsink, well, let's just say you want to insinuate someone else is dumb? :)
    I used to have the Corsair modules with lights on top showing activity, and while I mainly bought them for looks, they were actually useful at times to be able to quickly check if my system had totally crashed or was still doing stuff (you can sort of see the difference in the patterns in the lights).
  • knedle - Monday, July 25, 2011 - link

    I would love to see graphs showing how much power do different ram modules consume, few weaks ago I build low power computer with Sandy Bridge and I'm still looking into how to get as much from it as possible, with as low power consumption as possible.
  • Rajinder Gill - Monday, July 25, 2011 - link

    Power savings for DRAM are generally small. As you lower the current draw (either by reducing voltage or slacker timings) you are battling in part against the efficiency curve of the VRM.

    On some boards the difference in power consumption between DDR3-1333 and DDR3-1866 (given voltage and timing changes) can be as little as 1 Watt.

    -Raja
  • Vhozard - Monday, July 25, 2011 - link

    "Multiple passes are generally used to ensure the highest quality video output, and the first pass tends to be more I/O bound while the second pass is typically constrained by CPU performance."

    This is really not true, multiple passes are used by x264 to come as close as possible to a given file size. A one-pass crf-based encode produces an equally high quality video output, given the same conditions.

    Maybe you should use one-pass encodes, as they are more commonly used when file size specification is not very important.
  • JarredWalton - Monday, July 25, 2011 - link

    Multiple passes produce higher quality by using a higher bitrate where it's needed and a lower bitrate where it's not. In a single-pass, constant bitrate encode, scenes where there's a lot of movement will show more compression artifacts. There's no need to do multiple passes for size considerations: you do a constant bitrate of 2.0Mbps (including audio) for 120 minutes and you will end up with a file size of very close to 1800MB (or if you prefer, 1717.61MiB). Variable bitrate with a single pass doesn't have an accurate file size.
  • Vhozard - Monday, July 25, 2011 - link

    Very few people still use constant bitrate encodes.
    x264 works with a crf (constant rate factor), which gives constant *quality*; not constant bitrate!

    There is very much a need to do multiple passes for size considerations as a constant bitrate will not give them optimal quality at all.

    The quality between a crf (one-pass) of 15 that reaches a filesize of lets say 1 GBwill have almost exactly the same quality as a two-pass which is set at 1 GB.

    I suggest you read the x264 wiki...
  • JarredWalton - Monday, July 25, 2011 - link

    Sorry -- missed that you said CRF and not CBF.

Log in

Don't have an account? Sign up now