200 / 266 / 333 / 400 Straps
I've tested and thought some more on the 200 strap....
The main issue with tRD and cL combinations in certain FSB ranges, is non-allowable combinations for POST, resulting from MCH minimum timing limitations.
Earlier tests showed that the 200 strap allowed a lower tRD value to be used for a given CL etc, compared to what 266 and 333 straps would allow for POST.
eg: 200 strap allows POST/stability with CL7/tRD5, but 266 and 333 straps only allow minimum tRD6 with CL7.
Regardless of whether it works for DDR3, the existing (DDR2) tRD equation doesn't include a discrete reference to the Strap in use (other than including the divider in use). There would seem no allowance in the equation to predict the differences in POST behaviour, when using 1:2 divider on different straps.
Yet on this board there are differences in Strap/tRD POST allowability, which also seem independent of FSB (in 400-500FSB range I tested).
Despite the 200 strap allowing lower tRD values to POST, I would guess that the minimum allowable MCH timing (for POST) may not actually be lower on the 200 strap.
If lower allowable MCH latency resulted from using the 200 strap, then 200strap/CL8/tRD6 would be faster than 266 or 333 strap with CL8/tRD7.
Instead (I suspect), some other latency is introduced/forced by the 200 strap, which even with a lower tRD value, does not fall below the net minimum time for allowable POST.
If it's something along those lines, a forced increase in overall MCH latency (as suspected of the 200 strap) may allow POST/stability with lower tRD value (than 266 and 333 straps allow), but may not actually be better than neutral in terms of net MCH 'bandwidth' and/or stability, compared to other 'tighter' straps with higher minimum allowable tRD.
According to Everest, the 200 strap as tested gives lower performance, tRD for tRD, than 266 or 333 straps, with similar low performance apparent on the 400 strap too.
This doesn't mean that the 200 strap isn't worth using - it may be more stable - just that any expected benefit of allowing lower tRD values, may not come with it.
slowly piecing it together I hope, but just from incomplete information/knowledge :)
475x9 / 950 / 1:2 / CL8 / CT Strong / tRD6 / 200 strap
http://i447.photobucket.com/albums/q...24_PL6s200.jpg
475x9 / 950 / 1:2 / CL8 / CT Strong / tRD7 / 200 strap
http://i447.photobucket.com/albums/q...24_PL7s200.jpg
475x9 / 950 / 1:2 / CL8 / CT Strong / tRD7 / 266 strap
http://i447.photobucket.com/albums/q...24_PL7s266.jpg
475x9 / 950 / 1:2 / CL8 / CT Strong / tRD7 / 333 strap
http://i447.photobucket.com/albums/q...24_PL7s333.jpg
475x9 / 950 / 1:2 / CL8 / CT Strong / tRD7 / 400 strap
http://i447.photobucket.com/albums/q...24_PL7s400.jpg
ClockTwister comparison (200 strap)
200 Strap - Read boost for CL8/1:2 at 500FSB
Another strap-performance update guys - minor but useful maybe:
Read and Latency performance at 500FSB/CL8/1:2 (CT Strong)
As posted before, at 475FSB, 200strap/tRD6 and 333strap/tRD7 give equal Read and Latency with CL8, but 400/tRD7 Read and Copy are lower / Latency higher.
Unlike 200 strap at certain CL/FSB, the 400 strap does not allow lower tRD than 333 strap.
200 strap still allows CL8/tRD6 at 500FSB/1:2
Unlike results at 475FSB, CL8/tRD6 at 500FSB gives higher Read than 333 strap/CL8/tRD7. 400strap/tRD7 still has lowest Read and Copy / highest Latency.
Allowing CL8/tRD6, the 200 strap is able to give Read performance more comparable with 475FSB/CL7/tRD6 on 266 or 333 straps (EDIT: for same CPU clock).
The 500FSB/200 strap advantage is not available with CL7, as 200strap/1:2/CL7/tRD5 is disallowed before 450FSB
Consistent with a load increase, 500fsb/CL8 using 200 strap/tRD6, appears to need higher min vNB for same Large FFT (in)stability, compared to 333strap/tRD7.
500x8 / 1000 / 1:2 / CL8 / CT Strong
tRD7 / 400 strap
http://i447.photobucket.com/albums/q...400_CS_EV1.jpg
tRD7 / 333 strap
http://i447.photobucket.com/albums/q...333_CS_EV1.jpg
tRD6 / 200 strap
http://i447.photobucket.com/albums/q...200_CS_EV1.jpg