Memory Scaling on Haswell CPU, IGP and dGPU: DDR3-1333 to DDR3-3000 Tested with G.Skillby Ian Cutress on September 26, 2013 4:00 PM EST
The major enthusiast memory manufacturers are all playing a MHz race, to retail the most MHz possible. These are pretty much all Hynix MFR memory kits, known for their high MHz, but these kits are still binned in their thousands to get one or two modules that hit the high notes. With Haswell memory controllers happily taking DDR3-2800 in their stride, it all boils down to how useful is this increase in memory versus the price at which it costs to bin and produce.
In terms of competitive overclocking, the results are real – where every MHz matters and performance is not on the menu, enthusiasts are happy to take this high end kits to over 4000 MHz+ (recent news from G.Skill shows 4x4GB DDR3-4072 in Ivy Bridge-E, the fastest result ever in quad channel). The reality of that memory is often that enthusiasts are not purchasing but are being seeded the memory, taking the cost-effectiveness out of the ratio.
In terms of real world usage, on our Haswell platform, there are some recommendations to be made.
Avoid DDR3-1333 (and DDR3-1600)
While memory speed did not necessarily affect our single GPU gaming results, for real-world or IGP use, memory speed above these sinks can afford a tangible (5%+) difference in throughput. Based on current pricing, after the Hynix fire, it may be worthwhile, as memory kits above DDR3-1600 are now around the same price.
MHz Matters more than tCL, unless you compare over large MHz ranges
When discussing memory kits, there is often little difference in our testing when comparing different Command Rate numbers – the only issues ever came along with DDR3-1333 C9 and DDR3-1600 C11, which we already suggested are best avoided. Even still, above DDR3-2400 the benefits are minimal at best, with perhaps a few % points afforded in multiple GPU setups.
However, tCL might play a role when comparing large MHz differences, such as 2400 C12 vs. 1866 C8. In order to provide an apt comparison, I mentally use a ‘performance index’, which is a value of MHz divided by tCL:
As a general rule, below 2666 MHz, my Performance Index provides an extremely rough guide as to which kits offer more performance than others. In general we see 1333 C7 > 1333 C9, but 1333 C7 is worse than 2133 C11, for example.
When presented with two kits, calculate this Performance Index. If the kits are similar in number (within 10%), then take the kit with the higher MHz. If we take the results of Dirt 3 minimum frame rates in a CFX configuration, and plot against the Performance Index listed above, we plot the following curve:
The graph shows the trend of diminishing returns in this benchmark - as the PI is higher, we reach an asymptotic limit. Note the several results below the line at PIs of 167, 190 and 229 - these are the 1333 MHz memory kits, reinforcing the idea that at similar PI values, the higher MHz kit should be the one to go for.
Of course, cost is a factor – price raises more with MHz than with tCL, thus the ‘work benefit’ analysis comes in – if buying a kit boosts your productivity by x percent, how long will it take to recover the cost? In single GPU gaming, for our setup, the benefits seemed to be minimal, but I can see workload improvements going for something faster than 1600 C9.
Remember the Order of Importance
As I mentioned at the beginning of this overview, the order of importance for memory should be:
1. Amount of memory
2. Number of sticks of memory
3. Placement of those sticks in the motherboard
4. The MHz of the memory
5. If XMP/AMP is enabled
6. The subtimings of the memory
I would always suggest a user buy more memory if they need it over buying a smaller amount of faster memory. For gamers, common advice to hear on forums is to take sum of the memory of your GPUs and add 4GB or so for Windows 7/8 – that should be the minimum amount of memory in your system. For most single GPU gamers that would put the number at 8GB (for anything bar a Titan or dual GPU), or dual GPU gamers, above 8GB (suggestion is to stick to a power of two).
G.Skill 2x4GB DDR3-3000 12-14-14 1.65V Kit: Do we need it?
Firstly, many thanks to G.Skill for the memory kit on which these tests were performed – 3000 MHz on air can be a tough thing to do without a kit that is actually rated do it. This kit has done the rounds on all the major Z87 overclocking motherboards, including the ASRock Z87 OC Formula in this test.
On the face of it, investing in this kit means a small bump to BCLK, which has additional performance gains purely based on bus speed even at a slightly lower CPU multiplier. Beyond this, there are only very few scenarios where DDR3-3000 C12 beats anything 5x cheaper – a couple of our IGP compute benchmarks, a couple of IGP gaming scenarios and a couple of tri-GPU Crossfire games as well. However, the argument then becomes if going for the extra cost of the memory is not worth buying a discrete GPU outright (or better GPUs).
The memory kit has one thing going for it – overclockers aiming for high MHz love the stuff. In our testing, we hit 3100 C12 stable across the kit for daily use, one of the sticks hit 3300 MHz on air at very loose timings, and fellow overclocker K404 got one of the sticks to 3500 MHz on liquid nitrogen. In the hands of overclockers with much more time on their hands (and knowledge of the subsystem), we have seen DDR3-4400 MHz as well.
At $690 for a 2x4 GB kit, veteran system builders are laughing. It is a high price for a kit that offers little apart from a number parade. Perhaps the thing to remember is that plenty of memory manufacturers are also aiming at high MHz – Corsair, Avexir, TeamGroup, Apacer and others. If I had that money to spend on a daily Haswell system, I might plump for 4x8GB of DDR3-2400 C10 and upgrade the GPU with money left over.
For discrete GPU users, recommending any kit over another is a tough call. In light of daily workloads, a good DDR3-1866 C9 MHz kit will hit the curve on the right spot to remain cost effective. Users with a few extra dollars in their back pocket might look towards 2133 C9/2400 C10, which moves a little up the curve and has the potential should a game come out that is heavily memory dependent. Ultimately the same advice also applies to multi-GPU users as well as IGP: avoid 1600 MHz and below.
One relevant question to this is whether memory speed matters in the laptop space. It remains an untapped resource for memory manufacturers to pursue, mainly because it is an area where saving $5 here and there could mean the difference between a good and great priced product. But even when faced with $2000+ laptops, 1333 MHz C9 and 1600 C9-11 still reign supreme. I have been told that often XMP is not even an option on many models, meaning there are few opportunities for some pumped up SO-DIMM kits that have recently hit the market.
One point I should address which I failed to in the article. XMP rating for a memory kit are made for the density of that kit - i.e. a 2x8 GB DDR3-2400 C11 memory kit might not be stable at 2400 C11 when you add the two kits together in the same system. If a kit has a lot of headroom, then it may be possible, but this is no guarantee. The only guarantee is if you purchase a single kit (4x8 2400 C11, for example) then it will be confirmed to run at the rated timings. This in certain circumstances may be slightly more expensive, but it saves a headache if the kits you buy will not work in a full density system. I would certainly recommend buying a single kit, rather than gambling with two lower density kits, even if they are from the same family. The rating on the kit is for the density of that kit.
Post Your CommentPlease log in or sign up to comment.
View All Comments
Nagorak - Thursday, September 26, 2013 - linkWhy did memory prices fluctuate so much since the end of last year and now? The Hynix fire looks to have next to no impact, but the price of memory has nearly doubled since last November/December.
aryonoco - Thursday, September 26, 2013 - linkIan, I do not want to disparage your work, please take this as nothing but constructive criticism. You do amazing work and the wealth of technical expertise is very clear in your articles.
But you have a terrible writing style. There are so many sentences in your articles that while technically grammatically correct, are the most awkward ways of saying what you mean. Take a very simple sentence: "In terms of real world usage, on our Haswell platform, there are some recommendations to be made." There are so many ways, much simpler, much cleaner, much shorter to say what you said in that sentence.
I really struggle with your writing style. I know journalism isn't really your day job and you have a lot of important things to attend to, but please, if you care about this side job of yours as a technical writer, being technical is only half the story. Please consider improving your writing style to make it more readable.
Bob Todd - Friday, September 27, 2013 - linkI'd wager most of the readers didn't struggle as mightily as you. If you want to critique another's wordsmithery, you might want to find a classier way to do it. Our first exhibit will be sentence one of paragraph two. Surely you could have strung together a couple of words that got your point across without sounding like an ass?
Impulses - Friday, September 27, 2013 - linkYeah, I'm pretty sure that starting a sentence with a But is something you'd typically avoid...
Dustin Sklavos - Friday, September 27, 2013 - link"You have a terrible writing style."
How would you like it if someone came to your place of business and told you "Look, I don't mean to disparage your work, but it makes my cat's hair fall out in clumps."
ingwe - Friday, September 27, 2013 - linkYep. This definitely wasn't constructive.
Ian, I don't see anything wrong with your writing, and I would rather you concentrate on getting articles out than on spending lots of extra time on editing your work.
jaded1592 - Sunday, September 29, 2013 - linkYour first sentence is grammatically incorrect. Stones and glass houses...
Sivar - Thursday, September 26, 2013 - linkWhat a great article. Tons of actual data, and the numerous charts weren't stupidly saved as JPG. I love Anandtech.
soccerballtux - Thursday, September 26, 2013 - linkso bandwidth starved apps with predictable data requests (h264 p1) really like it but when the CPU has enough data to crunch (winrar) the lower real-world latency time in seconds is worth having.
gandergray - Thursday, September 26, 2013 - linkIan: Thank you for the excellent article. You provide in depth and thorough analysis. Your article will undoubtedly serve as a frequently referenced guide.