glitch said:
I think we've sort of established that dividers don't affect performance as much as people might think, but I'd imagine that they do come into play when you want to get the best out of your memory - you want to run a divider that will allow you to get the best from both your processor and your memory, but not necessarily by running them at 1:1?
Second part - timings.
I'm beginning to understand what the four numbers relate to, but what I don't understand is what makes a good combination and how the memory speed comes into it. If you had memory running at 2-2-2-2 (theoretically speaking, obviously) would memory doing those timings at 200Mhz be worse than memory running at 250Mhz? Assuming for the sake of this example that some would!
Have a read of this and decide for yourself how much impact memory overclocking has on the AMD64 platform:
http://www.neoseeker.com/Articles/Hardware/Guides/athlon64oc/
Re: Timings.
Each number refers to a clock cycle. The higher the frequency of the memory (200Mhz, 250 Mhz etc) the shorter the clock cycle.
e.g.
2 clock cycles @ 200 Mhz = 2 * (1000/200) = 10ns
2 clock cycles @ 250 Mhz = 2 * (1000/250) = 8ns
Another thing to remember is that lower numbers don't mean better performance for all the timings. Some are more stability settings and there will be an optimal number:
tCL (more commonly called CAS) = 1.5 (rare), 2, 2.5 or 3 (slow). Recommend 2 if possible, 2.5 if that's not possible.
tRCD (or RAS to CAS delay) = 2, 3 or 4. Recommend 2 or 3. 4 is pretty slow.
tRP (Row Precharge) = 2, 3 or 4. Recommend 2 or 3. 4 is pretty slow.
tRAS (Active to Precharge Delay) = large variety of numbers. Highly recommend using the following formula:
tRAS = tCL + tRCD + 2
or
tRAS = tCL + tRCD + tRP
In an ideal world, you'd be running the memory @ 300 Mhz or so @ 2-2-2-6 timings
However, often, running the memory at a high frequency can hold back your maximum stable overclock on the CPU (on-die memory controller). On the AMD64 platform, you should never sacrifice CPU clockspeed for memory clockspeed.
e.g. in my sig, I have quite a high CPU clockspeed (not as high as I'd like

) but a relatively low memory clockspeed with tight timings.
Hope some of this helps.