N
Nil Einne
Got a new system and currently working out what to run my memory at.
I'm mainly doing stability testing at the moment but having trouble
working out what to aim for and what to avoid. I thought it was
mostly, the lower the better but now know I was mistaken so need so
advise.
I have a DFI Infinity Ultra board which has the following settings:
T(RAS) = Active to Precharge delay
T(RCD-Read) = RAS to CAS delay for reads
T(RCD-Write) = RAS to CAS delay for writes
T(RP) RAS Precharge delay
CAS latency
T(RC) = bank cycle time
T(RPC) = refresh row cycle time
I have discovered from Mushkin that T(RAS) should never be lower then
T(RCD)+CAS+2 cycles for stability and performance. This was actually
quite significant since I seemed to be able to get reliable MemTest86
operation at outrageously low settings (3), but no one else had done
this and my memory has problems doing CAS latency of 2.0 at 200mhz so
it can't be super good so I realised there must be something wrong.
However, one thing I would like to know is is there any harm in
running RCD-Read and RCD-Write async other then potential stability
issues. Is there any advantage in running RCD-Write lower since from
what I can gather RCD-Read is what is important (I am able to run
RCD-Write at 2 but RCD-Read needs to be 3)?
Also, is there any reason I would want to adjust RC and RPC?
And could someone give some info on what will really help and in what
situations? I've come across numerous reviews put they all seem to
conflict each other. Some suggest CAS latency is the most important
but other people have found CAS 2.0 is unnessary on Nforce2 since
CAS2.5 is nearly the same.
Finally, is SiSoftSandra useful in determing performance (so I can
analyse e.g. a trade off of reducing FSB but improving timings)? Does
it really cover the wide range of demanding apps I'm likely to use
like video encoding, games etc? I don't believe it's a matter of pure
memory bandwidth since from what I've read there are other factors
that come into play as well.
I'm mainly doing stability testing at the moment but having trouble
working out what to aim for and what to avoid. I thought it was
mostly, the lower the better but now know I was mistaken so need so
advise.
I have a DFI Infinity Ultra board which has the following settings:
T(RAS) = Active to Precharge delay
T(RCD-Read) = RAS to CAS delay for reads
T(RCD-Write) = RAS to CAS delay for writes
T(RP) RAS Precharge delay
CAS latency
T(RC) = bank cycle time
T(RPC) = refresh row cycle time
I have discovered from Mushkin that T(RAS) should never be lower then
T(RCD)+CAS+2 cycles for stability and performance. This was actually
quite significant since I seemed to be able to get reliable MemTest86
operation at outrageously low settings (3), but no one else had done
this and my memory has problems doing CAS latency of 2.0 at 200mhz so
it can't be super good so I realised there must be something wrong.
However, one thing I would like to know is is there any harm in
running RCD-Read and RCD-Write async other then potential stability
issues. Is there any advantage in running RCD-Write lower since from
what I can gather RCD-Read is what is important (I am able to run
RCD-Write at 2 but RCD-Read needs to be 3)?
Also, is there any reason I would want to adjust RC and RPC?
And could someone give some info on what will really help and in what
situations? I've come across numerous reviews put they all seem to
conflict each other. Some suggest CAS latency is the most important
but other people have found CAS 2.0 is unnessary on Nforce2 since
CAS2.5 is nearly the same.
Finally, is SiSoftSandra useful in determing performance (so I can
analyse e.g. a trade off of reducing FSB but improving timings)? Does
it really cover the wide range of demanding apps I'm likely to use
like video encoding, games etc? I don't believe it's a matter of pure
memory bandwidth since from what I've read there are other factors
that come into play as well.