Memory Performance: 16GB DDR3-1333 to DDR3-2400 on Ivy Bridge IGP with G.Skill
by Ian Cutress on October 18, 2012 12:00 PM EST- Posted in
- Memory
- G.Skill
- Ivy Bridge
- DDR3
When it comes to memory overclocking, there are several ways to approach the issue. Typically memory overclocking is rarely required - only those attempting to run benchmarks need worry about pushing the memory to its uppermost limits. It also depends highly on the memory kits being used - memory is similar to processors in the fact that the ICs are binned to a rated speed. The higher the bin, the better the speed - however if there is a demand for lower speed memory, then the higher bin parts may be declocked to increase supply of the lower clocked component. Similarly, for the high end frequency kits, less than 1% of all ICs tested may actually hit the speed of the kit, hence the price for these kits increase exponentially.
With this in mind, there are several ways a user can approach overclocking memory. The art of overclocking memory can be as complex or as simple as the user would like - typically the dark side of memory overclocking requires deep in-depth knowledge of how memory works at a fundamental level. For the purposes of this review, we are taking overclocking in three different scenarios:
a) From XMP, adjust Command Rate from 2T to 1T
b) From XMP, increase Memory Speed strap (e.g. 1333 MHz -> 1400 -> 1600)
c) From XMP, decrease main sub-timings (e.g. 10-12-12 to 9-11-11 to 8-10-10)
There is plenty of scope to overclock beyond this, such as adjusting voltages or the voltage of the memory controller. As long as a user is confident with adjusting these settings, then there is a good chance that the results here will be surpassed. There is also the fact that individual sticks of memory may perform better than the rest of the kit, or that one of the modules could be a complete dud and hold the rest of the kit back. For the purpose of this review we are seeing if the memory out of the box, and the performance of the kit as a whole, will work faster at the rated voltage.
In order to ensure that the kit is stable at the new speed, we run the Linpack test within OCCT for five minutes. This is a small but thorough test, and we understand that users may wish to stability test for longer to reassure themselves of a longer element of stability. However for the purposes of throughput, a five minute test will catch immediate errors from the overclocking of the memory.
With this in mind, the kits performed as follows:
F3-1333C9Q-16GAO - rated at DDR3-1333 9-9-9-24 2T 1.50 volts
Adjusting from 2T to 1T: Passes Linpack
Adjusting from 1333 to 1400: Passes Linpack
Adjusting from 1333 to 1600: No Boot
Adjusting from 9-9-9 to 8-8-8: Linpack Error
F3-12800CL9Q-16GBXL - rated at DDR3-1600 9-9-9-24 2T 1.50 volts
Adjusting from 2T to 1T: Passed Linpack
Adjusting from 1666 to 1800: No boot
Adjusting from 9-9-9 to 8-8-8: No boot
F3-14900CL9Q-16GBSR - rated at DDR3-1866 9-10-9-28 2T 1.50 volts
Adjusting from 2T to 1T: Passes Linpack
Adjusting from 1866 to 2000: No boot
Adjusting from 9-10-9 to 8-9-8: No boot
F3-17000CL9Q-16GBZH - rated at DDR3-2133 9-11-10-28 2T 1.65 volts
Adjusting from 2T to 1T: Passes Linpack
Adjusting from 2133 to 2200: Passes Linpack
Adjusting from 2133 to 2400: No Boot
Adjusting from 9-11-10 to 9-9-9: No boot
Adjusting from 9-11-10 to 8-11-10: No boot
F3-2400C10Q-16GTX - rated at DDR3-2400 10-12-12-31 2T 1.65 volts
Adjusting from 2T to 1T: Passes Linpack
Adjusting from 2400 to 2600: No boot
Adjusting from 10-12-12 to 9-11-11: No boot
Facebook
Twitter
RSS
114 Comments
View All Comments
andrewaggb - Friday, October 19, 2012 - link
Fair enough :-)HisDivineOrder - Thursday, October 18, 2012 - link
You "remember" getting your first memory kit and it was for a E6400. You act like that's just this classic thing.I remember getting a memory kit for my Celeron 300a. I remember getting a memory kit for my AMD K6 with 3dNow!.
Wow, I'm old.
silverblue - Thursday, October 18, 2012 - link
I remember getting a 64MB PC100 DIMM in 2000... it was pretty much £1 a MB. Made a difference, so it was *gulp* worth it.StormyParis - Thursday, October 18, 2012 - link
Very interesting read. Thank you.rscoot - Thursday, October 18, 2012 - link
I remember paying upwards of $400 for a pair of matched 2x512MB Kingston HyperX modules with BH-5 chips. Those were the days! 300MHz at 2-2-2-5 1T in dual channel if you could put enough volts through them. Nowadays I don't think memory matters nearly as much as it did back then.superflex - Thursday, October 18, 2012 - link
Your first kit was an E6400?Let me know when you get hair down there.
My first computer was an Apple IIe in 1984, and my first build was an Opteron 170 with 400 MHz 2,2,2,5 DDR.
Magnus101 - Thursday, October 18, 2012 - link
Once again this only confirms that memory speed makes no real world difference.I mean, who in their right mind use the integrated GPU on an expensive i7-system to play metro-2033 with single digit framerate?
The only thing standing out is the Winrar compression, but, how many use winrar for compression?
Yes to decompress files it is very common but I only remember using it 2-3 times in my whole life to compress my own files.
So that isn't important to most users, except for the ones that actually use winrar to compress files.
And I don't get why the x264 encoding seemed like a big deal. The differences were very small.
It's beem the same story all the way back to the late 90;s were tests between sdr memory at 100 and 133 MHz or at different timings showed no differences in real life applications in contrast to synthetics.
But sure, if you are building a new system and choose between, let say 1333 or 1600, then a $5 difference is a no brainer.
Then again, it would make no noticeable difference anyway.
silverblue - Thursday, October 18, 2012 - link
Here's one - will it affect QuickSync in any way?twoodpecker - Monday, October 22, 2012 - link
I'd be interested in QuickSync results too. In my experience, not proven, it makes a big difference. I adjusted my memory speeds from 1600 to 2000 and noticed at some point that encoding is 25x instead of 15x. This might be due to different factors though, like software optimizations, because I didn't benchmark after adjusting mem speeds.Geofram - Thursday, October 18, 2012 - link
I don't believe he's implying that single digit frame rates on a game are going to real-life usable for anyone. I believe the point of the test was simply: "Lets take a system that is generally fast and put it in a situation where the IGP is being stressed. This will be the best-case scenario for faster RAM helping it. Lets see if it does".To me the idea was not showing everyone everyday situations where faster RAM will help them, instead it was to see where those situations might lay, by setting up a stressful situation and seeing the results. Most of the results were extremely small differences.
I agree it's not a noticeable difference in most cases. It doesn't make me feel like I should get rid of PC1333 RAM. I don't fault the logic for the tests used however. It was nice to see someone actually comparing the slight differences caused by RAM speed.