[huskerlug] Re: X

If it's concerning you, you might be able to reduce the amount of memory
X has access to if you've enabled the /proc filesystem.

This would be accomplished by changing the value in
/proc/sys/kernel/shmmax to something more in line with what you think
the maximum amount of memory X should be using.

I don't know if this works for X, but I know it works on postgres (where
I had to increase the value to prevent thrashing).  I also don't know
how safe this is to do on a running box.  I echo the size string to that
file on startup.

Of course, by limiting the amount of memory X has access to, you may
notice some degredation in performance, for the reasons that Mr. Eder
noted.  

There's probably a better way to handle this (uneducated tweaking of
/proc stuff has led to some Very Bad Days for me).  

Andrew Holm-Hansen

On Tue, 2003-06-17 at 15:12, David William Eder wrote:
> Actually, having all of your memory used up is a good thing.  Linux
> operates differently from Windows.  Windows sets aside a specific amount
> of memory for caching.  When it runs out, it lets go of some stuff.  Linux
> uses all available memory for caching.  It lets go of stuff when a program
> needs to use some memory.  So, in Linux the less free memory, the better
> performance you can expect for loading and unloading programs and data.
> 
> David.
> 
> 
> ----
> Husker Linux Users Group mailing list
> To unsubscribe, send a message to huskerlug-request@xxxxxxxxxxxxx
> with a subject of UNSUBSCRIBE
> 


----
Husker Linux Users Group mailing list
To unsubscribe, send a message to huskerlug-request@xxxxxxxxxxxxx
with a subject of UNSUBSCRIBE

Other related posts: