Gskill Ripjaws Overclocking

Status
Not open for further replies.

bajaj151

Contributor
I have 2*2GB G Skill Ripjaws CL7 1600mhz (Blue one) but it's running at 1333mhz (Motherboard: MSI 890GXM)

1) How can I overclock it to run at 1600mhz ?
2) Is it safe to overclock ?
3) Will there be any noticeable performance difference,if I overclock ?
 
The BIOS should have a setting that lets you run it at 1600MHz (some BIOSes will indicate 800MHz as the correct speed). This is because DDR3 only has official JEDEC speed rating of 1333Mhz so all RAM above that has to run in overclock mode.

Some AMD CPUs have problems with very low latencies. If it isn't stable at CL7, try setting it at CL8. The two settings may not be available on the same page in the BIOS.

You will get a noticeable bump in performance with the higher RAM speed. This was fairly apparent even on my puny little 2GB stick of DDR3 1333 RAM, when bumped to 1600Mhz it felt a lot better than a system with just 2GB of memory.
 
IIRC the AMD memory controller was bandwidth starved and showed slightly different results.

The trouble with the benchmarks you list is that as memory speed climbs, the latency climbs too. Given the same latency (as in my case) the higher speed brings additional benefits.

Memory is about access, so a tradeoff between speed and latency is like using a very small towel to cover yourself. something begins to show at either end. You can see the effect of the lower latency kit even in the benchmarks provided.

'Much' difference is subjective and depends on the benchmark. In real life memory is never really used the way a benchmark indicates it to. It is totally slaved to the operating system, and what you need for real objective memory evaluation is a AT-style (of old) multitasking test, which is possibly the closest you can get to real life.

It has been a much-repeated angst among memory enthusiasts that benchmarks never accurately capture real-life performance differences due to the extremely random nature of RAM use. Most benchmarks use a combination of short- and long-length random and streaming access, which is not really how Windows (for example) uses it.
 
Status
Not open for further replies.