1.9.125 (v2,. Beta 2) starts on Linux (RHEL4) in about 4 seconds---with
no special measures
David Teague wrote:
There have been articles about load time for OpenOffice.org
components. The consensus was that ooqstart-gnome or other
preloader could help. That didn't help me much, but Iike OO.o
so much that I would leave a compent loaded so the start time
is minimized. The following works well, and doesn't require
that you leave a copy of OO.o running.
There is an article in Linux Journal by Tom Adelstein on how
to speed up loading OpenOffice.org. Here is a link:
http://www.linuxjournal.com/article/8308
The author posted on the Ubuntu Users group
[EMAIL PROTECTED] the following
"You can add a quickstart applet to GNOME by installing the program
ooqstart- gnome, which may help some. However, an internal adjustment
to OOo Writer can improve the entire
suite's performance.
[Under Windows XP it cuts the load time from about 100 seconds
to about 20 seconds]
"To accomplish this, you need to start the word processor, Writer.
Next, you need to open the Tools drop-down menu and select options.
Once you open the options box, you are ready to adjust the memory and
speed up your Linux productivity suite. (see figure 3 in the article)
[The author evidently posted an image here, the Ubuntu list removed
it, but I followed the link above and figured out what he is saying.]
"In the above figure, you can see that we selected the first expansion
box and then clicked Memory with our mouse. This exposed the window
you see in Figure 3. I changed the default values under the Graphics
cache for Use for OpenOffice.org and Memory per Object. I increased
the first value from 6 to 128MB. I also increased the second value
from .5 to 20MB.
"After clicking OK, I closed the word processor and reopened it two
times. On each occasion, the application took less time to open. Under
Ubuntu, I found that OO Writer opened in three seconds, and in Fedora
it opened in less than six seconds. Previously, it took 30 and 26
seconds,
respectively, for the word processor to launch.
"NOTE: So people doubted the hack, but then others came back and said
it works absolutely.
It does work. But consider the other optimizations. "
This hack reduced startup time for my Windows system from an
annoying 15-20 seconds with the quick starter to 2 - 3 seconds
(also with the quick-starter).
It appears to me that you must have enough memory to support
both this and your other resident software for this to be successful.
Would someone please comment on this idea?
David Teague, http://cs.wcu.edu/~dbt
Advocating Free Software and Double Bass tuned in fifths
www.dennismasuzzo.com; www.silviodallatorre.com
www.joelquarrington.com/; For information on Red Mitchell,
http://home.teleport.com/~mimuma/; www.larryholloway.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
