- Apr 17, 2004
- 17,555
- 1
- 0
http://www.amdboard.com/athlon_64_3800_review_2.html
But is this guy saying that running the mem clock @ 216 with same CPU clock actually yields lower performance @ same timings vs mem clock @ 200? "Asynchronous mode?" I thought since there wasn't an FSB anymore that memory wouldn't have an advantage being "synchoronous" with HTT.....
Well, first off the writing in this article is just BAD, so damn confusing half the time. That may be part of my confusion.Cachemem memory and cache access latencies with the memory bus running synchronously at 400 MHz (solid blocks) or else at 433 MHz (transparent blocks) -- lower is better. All latency settings were identical. One issue we ran into originally was that upon increasing the memory frequency to 433, the CPU HT frequency increased (without any manual interference from 200 to 216 MHz) meaning that the CPU was running faster, apparently using the memory clock (433 MHz) as reference. We manually adjusted the clock back to 200 MHz and checked the performance using entirely CPU-centric benchmarks such as Caligari TrueSpace as well as by comparing the cache access latencies in cachemem as reference. The graph clearly shows a significant performance degradation resulting from running the memory bus faster - in asynchronous mode.
But is this guy saying that running the mem clock @ 216 with same CPU clock actually yields lower performance @ same timings vs mem clock @ 200? "Asynchronous mode?" I thought since there wasn't an FSB anymore that memory wouldn't have an advantage being "synchoronous" with HTT.....