DRAM Idle timer

  • Thread starter Thread starter Alb
  • Start date Start date
A

Alb

Hi all.
I have seen this setting that can go from [infinite] to [64T] or [AUTO]
What is it and what [64T] mean ?
What does it mean to set this value ti [infinite] ?
Thanks

Alb

My MOBO ASUS P4P800 SE
 
Hi all.
I have seen this setting that can go from [infinite] to [64T] or [AUTO]
What is it and what [64T] mean ?
What does it mean to set this value ti [infinite] ?
Thanks

Alb

My MOBO ASUS P4P800 SE

Check out this site if you don't know about it,
http://www.rojakpot.com/default.aspx?location=9

DRAM Idle Timer

Common Options : 0T, 8T, 16T, 64T, Infinite, Auto

Quick Review

This BIOS feature sets the number of idle cycles that is allowed before
the memory controller forces such open pages to close and precharge.

The premise behind this BIOS feature is the concept of temporal
locality. According to this concept, the longer the open page is left
idle, the less likely it will be accessed again before it needs to be
precharged. Therefore, it would be better to prematurely close and
precharge the page so that it can be opened quickly when a data request
comes along.

It can be set to a variety of clock cycles from 0T to 64T. This sets the
number of clock cycles the open pages are allowed to idle before they
are closed and precharged. There's also an Infinite option as well as an
Auto option.

If you select 0 Cycle, then the memory controller will immediately
precharge the open pages as soon as there's an idle cycle.

If you select Infinite, the memory controller will never precharge the
open pages prematurely. The open pages will be left activated until they
have to be precharged.

If you select Auto, the memory controller will use the manufacturer's
preset default setting.

Most manufacturers use a default value of 8T which allows the memory
controller to precharge the open pages once eight idle cycles have
passed.

For general desktop use, it is recommended that you choose the Infinite
option so that precharging can be delayed for as long as possible. This
reduces the number of refreshes and increases the effective memory
bandwidth.

For applications (i.e. servers) that perform a lot of random accesses,
it is advisable that you select 0T as subsequent data requests would
most likely be fulfilled by other pages. Closing open pages to precharge
will prepare those pages for the next data request that hits them.
There's also the added benefit of increased data integrity due to more
frequent refreshes.



hth,
Ed
 
Back
Top