On Thu, 2005-12-29 at 08:09 -0500, Ken Schneider wrote:
On Thu, 2005-12-29 at 14:08 +0200, Hans du Plooy wrote:
(which I think you addressed above). However, the 12s you mention -- that is not with a *tuned* OOo startup is it? No, I'm not aware of any tricks to tune OOo to start quicker, except for the quicklauncher, which I don't use because I don't want it hogging my memory when I'm not using OOo.
Then don't bitch about how s l o w it is to load. That is what the quickstarter is there for. It does the same thing MS does, it pre-loads the libs. Why do you think MS requires a reboot after installing new software, so windows can preload the DLL's and get the app to load faster. Which is why each new version of windows needs newer and faster hardware with more memory to run. Oh, and the quickstarter doesn't use -that- much memory.
from top: 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. -- Ken Schneider UNIX since 1989, linux since 1994, SuSE since 1998