NesuD
Diamond Member
- Oct 9, 1999
- 4,999
- 106
- 106
Originally posted by: screw3d
Umm.. so I'm running 7-2-3-2, with the 3 being the RAS to CAS access. Should I make it 6-2-3-2 instead?![]()
No, On Nforce 2 boards for whatever reason raising the TRAS delay actually improves memory perfomance. From looking at your rig specs I am assuming you are running the chip on a 200mhz bus setting. Do a memory bench like sandra or pcmark at your current settings then Change the TRAS to 11 and run the same benches again and you should see an improvement in the scores. Here is what Mushkin has to say on the subject also here is a link to a thread at [/quote]AMDMB.com that covers the subject.
"Memory, in many ways is like a book, you can only read after opening a book to a certain page and paragraph within that particular page. The RAS Pulse Width is the time until a page can be closed again. Therefore, just by definition, the minimum tRAS must be the RAS-to-CAS delay plus the read latency (CAS delay). That is fine for FPM and EDO memory with their single word data transfers. With SDRAM, memory controllers started to output a chain of four consecutive quadwords on every access. With DDR, that number has increased to eight quadwords that effectively are two consecutive bursts of four.
Now imagine someone closes the book you are reading from in the middle of a sentence. Right in your face! And does it over and again. This is what happens if tRAS is set too short. So here is the really simple calculation: The second burst of four has at least to be initiated and prefetched into the output buffers (like you get a glimpse at the headline in a book) before you can close the page without losing all information. That means that the minimum tRAS would be tRCD+CAS latency + 2 cycles (to output the first burst of four and make way for the second burst in the output buffers).
Any tRAS setting lower tRCD + CAS + 2 cycles will allow the memory controller to close the page ?in your face!? over and again and that will cause a performance hit because of a truncated transfer that needs to be repeated. Along with those hassles comes the self-explanatory risk for data corruption. That one is not a real problem as long as the system is kept running but in case it is shut down and the memory content is written back to the hard disk drive, the consequences can be catastrophic. For the drive, that is."