A question about use of RAM

  • Thread starter Thread starter FulanoDeTal
  • Start date Start date
F

FulanoDeTal

I was just noticing that when the headers (about 900 of them) for this
group were being downloaded, the HDD was crunching away continuously
in the process. Now, why can't the headers be loaded first into RAM,
spit out onto the screen, and then written to the drive? Is there a
way to set things up to do it that way? How?
 
from the said:
I was just noticing that when the headers (about 900 of them) for this
group were being downloaded, the HDD was crunching away continuously
in the process. Now, why can't the headers be loaded first into RAM,
spit out onto the screen, and then written to the drive? Is there a
way to set things up to do it that way? How?

If you enable write caching on the disk (physical disk drive,
properties, policies, tick the box) this will happen for all disk
writes. However it will still start writing (if the disk is idle) as
soon as it can, and probably before all the headers have downloaded, and
started to display.
 
If you enable write caching on the disk (physical disk drive,
properties, policies, tick the box) this will happen for all disk
writes. However it will still start writing (if the disk is idle) as
soon as it can, and probably before all the headers have downloaded, and
started to display.

OK. Thanx. I have write caching enabled. Funny, it's greyed out and
I can't change it. Why would that be?
 
from the said:
OK. Thanx. I have write caching enabled. Funny, it's greyed out and
I can't change it. Why would that be?

Maybe you're not an admin, maybe you're on a domain, and the domain
admin has locked out you ability to twiddle, maybe it's a feature of the
disk drivers you are using?
 
FulanoDeTal said:
OK. Thanx. I have write caching enabled. Funny, it's greyed out and
I can't change it. Why would that be?

Probably because you are using third party drivers that always do it
anyway (or *maybe* never do so) like the Intel Application Accelerator
ones
 
Back
Top