Issue 78534 - Memory settings done during install
Summary: Memory settings done during install
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 1.0.0
Hardware: All All
: P5 (lowest) Trivial with 2 votes (vote)
Target Milestone: ---
Assignee: AOO issues mailing list
QA Contact:
Depends on:
Reported: 2007-06-15 17:01 UTC by gemlog
Modified: 2013-02-07 22:33 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 gemlog 2007-06-15 17:02:00 UTC
Optimal memory setting make a huge difference in start-up times. No one really
does this or knows what is optimal. Could the installer not query the OS and set
this during install?
Comment 1 Olaf Felka 2007-06-15 17:09:35 UTC
Can you be more detaile what you think what should be done or not at startup?
Comment 2 gemlog 2007-06-15 17:26:31 UTC
There are numerous threads around the net where people propose different numbers
for the memory settings to speed things up. Use for and use per
object. Setting these large enough seems to speed start-up. No one seems to know
exactly what these numbers should be and most don't even know to try and set
them to something higher than the default. 
If the installer did a call to learn how much memory the system had, wouldn't it
be able to choose better numbers than the defaults? I think these settings have
long been there (even before ooo?) so I'm guessing the guys who maintain that
code know what would be optimal based on available system ram.
Comment 3 Olaf Felka 2007-06-15 17:36:35 UTC
Comment 4 gemlog 2007-06-15 17:37:53 UTC