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
‘How much does memory speed matter?’ is a question often asked when dealing with mainstream processor lines. Depending on the platform, the answers might very well be different. Similar to our comparisons with Ivy Bridge, today we publish our results for 26 different memory timings across 45 benchmarks, all using a G.Skill memory kit.
In our previous memory scaling article with an Ivy Bridge CPU, the results of memory testing between DDR3-1333 to DDR3-2400 afforded two main results – (a) the high end memory kit offered up to a 20% improvement, but (b) this improvement was restricted to certain memory limited tests. In order to be more thorough, our tests in this article take a single memory kit, the G.Skill 2x4GB DDR3-3000 12-14-14 1.65V kit, through 26 different combinations of memory speed and CAS latency to see if it is better to choose one set of timings over the other. Benchmarks chosen include my standard array of real world benchmarks, some of which are memory limited, as well as several gaming titles on IGP, single GPU and multi-GPU setups, recording both average and minimum frame rates.
The Problem with Memory Speed
As mentioned in the Ivy Bridge memory scaling article, one of the main issues with reporting memory speeds is the exclusion of the CAS Latency, or tCL. When a user purchases memory, it comes with an associated number of sticks, each stick is of a certain size, memory speed, set of subtimings and voltage. In fact the importance of order is such that:
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 use this order on the basis that point 1 is more important than point 3:
- A system will be slow due to lack of memory before the speed of the memory is an issue (point 1)
- In order to take advantage of the number of memory channels of the CPU we must have a number of sticks that have a factor of the memory channels (point 2), known as dual channel/tri channel/quad channel.
- In order to ensure that we have dual (or tri/quad) channel operation these sticks need to be in the right slots of the motherboard – most motherboards support two DIMM slots per channel and we need at least one memory stick for each channel
- If the MHz of the memory is more than CPU is rated for (1333, 1600, 1866+), then the user needs to apply XMP/AMP in order to benefit from the additional speed. Otherwise the system will run at the CPU defaults.
- Subtimings, such as tCL, are used in conjunction with the MHz to provide the overall picture when it comes to performance.
A user can go out and buy two memory kits, both DDR3-2400, but in reality (as shown in this review), they can perform different and have different prices. The reason for this will be in the sub-timings of each memory kit: one might be 9-11-10 (2400 C9), and the other 11-11-11 (2400 C11). So whenever someone boasts about a particular memory speed, ask for subtimings.
G.Skill DDR3-3000 C12 2x4GB Memory Kit: F3-3000C12D-8GTXDG
For this review, G.Skill supplied us with a pair of DDR3 modules from their TridentX range, rated at DDR3-3000. This is at the absolute high end of memory kits, with very few memory kits going faster in terms of MHz. Of course, in this MHz race, it comes at a price premium: $690 for 8 GB. This memory kit uses single-sided Hynix MFR ICs, known for their high MHz numbers, and while there are large heat-spreaders on each stick, these can be removed reducing the height from 5.4 cm to 3.9 cm.
Hynix MFR based memory kits are used by extreme overclockers to hit the high MHz numbers. Recently YoungPro from Australia took one of these memory sticks and hit DDR3-4400 MHz (13-31-31 sub-timings) to reach #1 in the world in pure MHz.
Intel Core i7-4770K Retail @ 4.0 GHz
4 Cores, 8 Threads, 3.5 GHz (3.9 GHz Turbo)
|Motherboards||ASRock Z87 OC Formula/AC|
Intel Stock Cooler (pre-testing)
|Power Supply||Corsair AX1200i Platinum PSU|
|Memory||G.Skill TridentX 2x4 GB DDR3-3000 12-14-14 Kit|
|Memory Settings||1333 C7 to XMP (3000 12-14-14)|
|Discrete Video Cards||
|Video Drivers||Catalyst 13.6|
|Hard Drive||OCZ Vertex 3 256GB|
|Optical Drive||LG GH22NS50|
|Case||Open Test Bed|
|Operating System||Windows 7 64-bit|
|USB 3 Testing||OCZ Vertex 3 240GB with SATA->USB Adaptor|
With this test setup, we are using the BIOS to set the following combinations of MHz and subtimings:
Almost all of these combinations are available for purchase. For any combination of MHz and CAS, we attempt that CAS for all sub-timings, e.g. 2400 9-9-9 1T at 1.65 volts. If this setting is unstable, we move to 9-10-9, 9-10-10 then 9-11-10 and so on until the combination is stable.
There is an odd twist when dealing with DDR3-3000. In order to reach 3000 MHz, as Haswell does not accept the DDR3-3000 memory strap, we actually have to use the DDR3-2933 strap and boost the CPU speed to 102.3 MHz. This leads to a slight advantage in terms of CPU throughput when using DDR3-3000 which does come through in several benchmarks. In order to keep things even, our 4.0 GHz CPU has the multiplier reduced for 3000 C12 in order to keep the overall system speed the same, albeit with a slight BCLK advantage.
At the time of testing, DDR3-3000 C12 was the highest MHz memory kit available, but since then there are now 3100 C12 memory kits on the market taking price margins even higher at $1000 for 8 GB. The problem at this speed is the actual overclocking of the CPU aspect of the system will skew the performance results in favor of the high end kit.
For this test, we use the following real world and compute benchmarks:
CPU Real World:
- WinRAR 4.2
- FastStone Image Viewer
- Xilisoft Video Converter
- x264 HD Benchmark 4.0
- TrueCrypt v7.1a AES
- USB 3.0 MaxCPU Copy Test
- 3D Particle Movement, Single Threaded and MultiThreaded
- SystemCompute ‘2D Explicit’
- SystemCompute ‘3D Explicit’
- SystemCompute nBody
- SystemCompute 2D Implicit
- SystemCompute ‘2D Explicit’
- SystemCompute ‘3D Explicit’
- SystemCompute nBody
- SystemCompute MatrixMultiplication
- SystemCompute 3D Particle Movement
For what should be obvious reasons, there is no point in running synthetic tests when dealing with memory. A synthetic test will tell you if the peak speed or latency is higher or lower – that is not a number that necessarily translates into the real world unless you can detect the type and size of all the memory accesses used within a real world environment. The real world is more complex than a simple boost in memory read/write peak speeds.
For each of the 3D benchmarks we use an ASUS HD 6950 (flashed to HD6970) for the single GPU tests, the HD 4600 in the CPU for IGP, and a HD 5970+5870 for a lopsided tri-GPU test.
- Dirt 3, Avg and Min FPS, 1360x768
- Bioshock Infinite, Avg and Min FPS, 1360x768
- Tomb Raider, Avg and Min FPS, 1360x768
- Sleeping Dogs, Avg and Min FPS, 1360x768
Firstly, I want to go through enabling XMP in the BIOS of all the major vendors.
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.