Memory acronyms

[Narc]

Iam so lost when it comes to memory acronyms and i didn't see anything in the FAQ so here they are.

TRC
TRFC
TRCD
TWR
TRWT
TRAS
TRP
TWCL

phew. Now of course i don't expect you all to explain them all(only if u want too). I just like to know which ones i can use to when OCing. Ive got a ASUS AV8 Deluxe with a a64 4000+ in it. Using geils pc-4200 mem.

thanks

 

[robberbaron]

http://www.ocforums.com/showthread.php?t=329627

This is a thread about DFI bios setting, but all of your questions are answered here in full detail.

 

[Qwertyman]

here's the one's you need:

CAS Latency , sometimes referred to as CL or CAS, is the minimum number of cycles the ram must wait until it can read or write again. Obviously, the lower the number (time), the better.

tRCD is the delay before the data on a particular row in memory is read/written. Again, the lower the number the better.

tRP is basically the precharge time of the row. tRP is the time the system waits after writing something to a row before another row can be active. Once again, lower is better.

tRAS is the minimum value for how long a row can be active. So basically, tRAS is how long the row has to be turned on. This number varies quite a bit with RAM settings.

 

[robberbaron]

There are others that are very important, like Max Async Latency. That needs to be as low as possible and I find that it has just as much impact as the "big four" on latency. Also, tRc should be as tight as possible, though raising it gets more stable OC's. tRas is weird. I find 12 to be the best for latency. I can run a tRas of 0, but it's worse latency than 12. Very strange timing.

 

[Qwertyman]

There are others that are very important, like Max Async Latency. That needs to be as low as possible. Also, tRc should be as tight as possible, though raising it gets more stable OC's. tRas is weird. I find 12 to be the best for latency. I can run a tRas of 0, but it's worse latency than 12. Very strange timing.

well true because that sweet spot thereom always comes into play.

 

[(cf)Eclipse]

TWR
TRWT
those two have a decent effect on write bandwidth.. and a64's are write bandwidth limited in my experience

 

[robberbaron]

TWR
TRWT
those two have a decent effect on write bandwidth.. and a64's are write bandwidth limited in my experience

Yeah, at my super 38.4ns 255MHz settings, I only got like 1522 in single channel.

iT cont rite gud but It con REED gud aT 3825 EN evarist.

 

[Narc]

So far my system is stable @ 2,3,3,5. Stock was 3,4,4,8. Noticed an increase slightly in si sandra. Also my stability is alot better when running prime95(100%), so far iam 2 hours in and still going @ 2.83ghz. Temp is alittle high at 48C(118F) but its under load so its not to bad.

Thanks for the english lesson lol.

 

[(cf)Eclipse]

latency is more important than bandwidth with a64's.
use everest to check the latency difference at 2-3-3 vs 3-4-4. i bet it's huge

 

[AMD T-type]

latency is more important than bandwidth with a64's.
use everest to check the latency difference at 2-3-3 vs 3-4-4. i bet it's huge

but doesn't lower latency give you more bandwidth ? o_0

 

[robberbaron]

but doesn't lower latency give you more bandwidth ? o_0

Slightly, but more MHz = more bandwidth than lower timings. And on a 939 DC setup, bandwidth does not really limit anything, just timings. You get way more performance out of 2-2-2-x than 3-4-4-x.