From the previous page we can conclude that Sandy Bridge loves high ram speeds. Though can we squeeze some more points or FPS out of it, when messing with the main RAM timings ? Let's start off with 1333Mhz. Yep I again ditched a RAM divider, as the 1066Mhz might be sort off interesting for laptop integrators. For desktop users it shouldn't even be an option to buy...
I used the 2500K on the same bench-suites of the previous pages. Testing the following timings :
For 1333Mhz and 1600mhz : CL6-6-6-18, CL7-7-7-21 and 8-8-8-24
For 1866 : CL7-7-7-21, CL8-8-8-24 and CL9-9-9-27
For 2133 : CL7-8-7-21, CL8-8-8-24 and CL9-9-9-27
1333Mhz is up first :
Both SuperPi 1M and Wprime 32 tests are very short and more in favour of raw CPU clocks. The differences are really small between Cas 6 and 8.
Superpi 32M almost gains about 7 seconds. Nothing shabby for a bencher, for a daily user the difference the gain is negligible.
AIDA64's memory benchmark only shows an improvement in the Read test. Write and Copy stay put. Maybe this will change with higher ram clocks.
Encoding a file into HD quality almost gains nothing either from faster timings. Not even a full FPS is won.
Cinebench improves also a tiny bit with the Cas 6 setting. Nothing earth shattering though
Finally a nice improvement : PCMark05 seems to like tighter timings. 300 points gain is really nice.
The Synthetic 3DMarks from Futuremark again show slightly better scores with tighter timings. Especially the 3DMark 01 score is improving with over 1000 points.
By limiting the resolution to 1280 x1024 our GTX 480 is CPU limited. The tiny gain observed will be not noticeable when upping resolutions and detail level. For a gamer if 1333Mhz is your weapon of choice , even Cas 8 will do nicely.
SuperPi and Pifast stable.