Normally you run with a 4X RDRAM multiplier, set in BIOS. When running on an external clock that is 133MHz or greater you can flip this to a 3X multiplier and not lose any memory bandwidth.
But, at this point you lose synchronosity which drastically reduces the efficiency of the memory bandwidth and memory bandwidth starving the processor. You will still see performance increases with major overclocks, but on a smaller scale than with synchronized CPU & RAM. This problem is exaggerated with the P4 as an asynch config has the FSB faster than the RAM, so the CPU ends up stalling while waiting for RAM. With Athlons you have the opposite effect in asynch situations, RAM faster than the CPU can use. Either way, you lose performance per clock.
Your RDRAM would be running at 469MHz, which is greater than the default 400MHz and is attainable with any old 400MHz DRCGs.
But to maintain synchronocity you would need to clock the RDRAM to 625MHz (1250 effective - yeah, RDRAM is DDR as well) to attain 2.5GHz on the proc as I stated in my previous post. This is not attainable by any RIMMs I have ever seen and probably won't be for a year.
The memory bandwidth offered by such a solution would be 3.752GB/s. The memory bandwidth offered by any DDR SDRAM solution for the same external clock and FSB would be less.
Correct, with current chipsets and motherboards (and why a NW 1.6A RDRAM based system makes good sense for the moment).
Dual-channel DDR-SDRAM (yeah, yeah, I know - beating the dead horse) would provide more bandwith. PC2100 would do 4266MBps and PC2700 would scale to 5333MBps memory bandwidth all without even stressing the RAM - allowing the memory to stay synchronous. Imagine the higher benchmarks and frame rates!
If you don't believe the performance hit you're taking because Intel doesn't want to admit they are wrong with RDRAM, try it:
Push your RDRAM based P4 system's FSB to 133Mhz (533 effective) and run your benchmarks. Now change your 4x FSB/memory multiplier to 3x and run them again. How much performance did you lose - 10%? More? That's about the same percentage as what you're losing by going asynch to reach 2.5GHz. Yes you still gain performance, so it's worth it, but wouldn't it be better to get the full potential of the chip?
I thought a thought, but the thought I thought wasn't the thought I thought I had thought.