flymoop :
yup FSB of 266 gives 1066 DRAM Freq, 320 gives 1067.
No
Definition time (attention purists, I'm talking about DDR2 and I'm simplifying a little
):
Core2 CPU's use a frontside bus (FSB). The FSB is a
thing with two main characteristics: speed which is usually defined in MHz and width which in the Core2's is 64 bits wide. We are concerned with the speed.
Using the Q6600 as an example, the FSB
frequency is 266 MHz. The matching DDR2
memory clock for that frequency is 533 MHz (266 X 2). DDR2 memory transfers two chunks of data for each bus cycle, hence double the frequency. So, to run 1:1 at an FSB of 266 MHz, we need DDR2-533 RAM. What CPUZ does is a little confusing. It will tell you that the memory
frequency is 266 MHz for a 1:1 ratio.
The FSB
clock is 1066 MHz (266 X 4). The bus is "quad pumped". It transfers 4 chunks of data into and out of the CPU each bus cycle. So each FSB cycle generates 4 FSB clocks.
Now, if you increase the FSB frequency to 333 MHz, the corresponding memory clock is 667 MHz and the FSB clock is 1333 MHz.
I always run my memory at 1:1. That is the FSB freq to mem freq ratio of one to one. That means that the memclock is twice the FSB freq. It's a little confusing. Running memory slower costs performance. Running memory faster does not give you much if any real world performance increase and it can lead to higher instability.
Some of us discuss that here:
http://www.tomshardware.com/forum/251715-29-ratio-myth
You will gain more performance by tightening memory timing than you will by trying to overclock your memory. The performance gain will not be visible without a good benchmark for memory i/o.