[prev in list] [next in list] [prev in thread] [next in thread] 

List:       suse-linux-e
Subject:    RE: [SLE] OO: If you can make it, I can break it!
From:       Ken Schneider <suse-list () bout-tyme ! net>
Date:       2005-12-29 23:29:23
Message-ID: 1135898963.8761.46.camel () pc5 ! bout-tyme ! net
[Download RAW message or body]

On Thu, 2005-12-29 at 21:03 +0100, Carlos E. R. wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> 
> The Thursday 2005-12-29 at 08:38 -0500, Ken Schneider wrote:
> 
> > 15578 ken       16   0 30728  19m  13m S  0.0  2.5   0:03.02 oooqs
> > 
> > looks like it is using all of 19m of memory which will go to
> > cache/buffers anyway if oooqs is not running so if you are concerned
> > about something "hogging" your memory look at what caching/buffering is
> > doing anyway, hogging ALL available memory which makes programs load
> >   s l o w e r  while trying to get memory for it's process. Perhaps if
> > there was a way to limit the amount of memory used by the cache/buffer
> > system it would help speed up the startup of programs.
> 
> Actually, the cache/buffer memory makes the system go faster. The more you 
> have there, the faster.
> 
> That's why the second time you load OOo, without the quickstarter, it 
> loads faster: it doesn't need to read from disk, it is already in memory.
> 

But -that- is the whole problem with "perception" with -new- users. They
load a program like OO and it takes them forever the first time and they
then think that -everything- runs slower. If there was a limit to how
much ram was used by cache/buffer, programs would load faster the
-first- time because memory would be available the first time it was
started. The "perception" that new users need to have is that linux is
as fast as MS Windows or better yet faster.
The cache/buffer use needs to be a tunable parameter.

-- 
Ken Schneider
UNIX  since 1989, linux since 1994, SuSE  since 1998


-- 
Check the headers for your unsubscription address
For additional commands send e-mail to suse-linux-e-help@suse.com
Also check the archives at http://lists.suse.com
Please read the FAQs: suse-linux-e-faq@suse.com


[prev in list] [next in list] [prev in thread] [next in thread]