I would really like to know why does linux access the >disk so much (in GUI mode) to fire-up even a small application like terminals >windows? What is it that it reads/writes so much? This is irrespective of >m/c configuration.
veejay
My swap is 4 times the RAM still i also face the same problem...
On Sun, 18 Jan 2004, xterm wrote:
My swap is 4 times the RAM still i also face the same problem...
is your swap on your hard disk or not? if it is, then maybe that explains why accessing the swap also accesses the hard disk. how much ram do you have?
An veejay spake thusly:
I would really like to know why does linux access the >disk so much (in GUI mode) to fire-up even a small application like terminals
windows? What is it that it reads/writes so much? This is
irrespective of >m/c configuration.
veejay
My swap is 4 times the RAM still i also face the same problem...
(wading in late, excuse)
What is the distribution ? What machine config ? More importantly do you have anything running in the background ? Excessive logging ? You have some inefficient program running in the background which updates a few KB file on disk every few seconds ? There could be many reasons. Your problem seems not to be a generally observed phenomenon.
With modern machines with more than 128Mb RAM I dont think you should have great problems. Gnome 2.2/KDE may require a bit of more RAM. Try not running XWindows and then see if the disk io continues. I suppose you gotta track down the problem first before searching for a solution.
-
Philip S Tellis -
q u a s i -
xterm