Issue 98700 - Better preload OOo components into memory
Summary: Better preload OOo components into memory
Alias: None
Product: performance
Classification: Code
Component: www (show other issues)
Version: current
Hardware: All All
: P3 Trivial with 2 votes (vote)
Target Milestone: milestone 1
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2009-02-01 12:54 UTC by jirkaz
Modified: 2013-02-07 22:41 UTC (History)
1 user (show)

See Also:
Latest Confirmation in: ---
Developer Difficulty: ---


Note You need to log in before you can comment on or make changes to this issue.
Description jirkaz 2009-02-01 12:54:32 UTC
I use OOo3 on Linux and Windows XP, P4/2,6GHz, 2GB RAM. First ("cold", after
system boot) start of any component (mainly Writer, Calc or Draw) is acceptable
on Linux (where it is faster), but not on WXP. On WXP it takes 15+ seconds
(sometimes 20 or more). I use Quickstarter feature, of course, but it seems me
it has no significant effect...

The later "hot" start (one or more OOo component was already open and files are
in memory) is very quick, somewhere about 1-2 sec.

I have following question (or suggestion): is it possible to improve the OOo
files preloading, probably greater amount of them into RAM? Maybe via
Quickstarter configuration (i.e. for example "selection of what component(s) of
OOo has to be preloaded") or via some other utility (external software)...

Simply, by other words: the expected result would be something like "open the
Writer (Calc, Draw..), close it, but all necessary files still in RAM", but the
whole process invisible (automatic during Windows startup). Or - once more - the
Quickstart improvement ;-)

I think most of today PC has sufficient size of RAM (1GB or more), that's why
such preloading wouldn't be problematic. The both processses together
(soffice.bin + soffice.exe) before hot start (i.e. after running + closing
Writer + Calc + Draw) have about 45MB in RAM - it is not so much... It would be
optional, after all, as described above.

Thank you.