Bug 46436 - LibreOffice Startup Times
Summary: LibreOffice Startup Times
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
Version:
(earliest affected)
3.5.0 release
Hardware: x86-64 (AMD64) Windows (All)
: low minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-02-22 02:26 UTC by weaselthatbites
Modified: 2014-06-18 13:55 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description weaselthatbites 2012-02-22 02:26:56 UTC
On every single machine I have ever installed Libreoffice it can take anywhere between 10 to 20 seconds to first startup Libreoffice. This is a very long time indeed for any program to take to startup. Even with the normal tips to make things start quicker such as enabling the quickstarter, reducing the amount of memory etc etc, it still takes ages.

However, I have found a way of reducing the loading time significantly. Way much more than anything else that has been suggested. 

Simply stopping the logo from starting up significantly reduced startup times:


 Before removing logo on my 64 bit Windows:
 Initial startup time (ie from a fresh boot) = 16 seconds
 Starting up any office document after that = 6 seconds


 After removing logo on my 64 bit Windows:
 Initial startup time (ie from a fresh boot) = 9 seconds
 Starting up any office document after that = 3 seconds


 Removing the logo/splash screen is easy:

 Go to C:\ Program files\Libre Office\Program [if your on a 64 bit version of windows, that would be Program Files (x86)]

 Open up soffice.ini which will look something like this:

 [Bootstrap]
 HideEula=1
 Logo=1
 NativeProgress=true
 ProgressBarColor=126,170,23
 ProgressFrameColor=207,208,211
 ProgressPosition=164,225
 ProgressSize=319,10
 URE_BOOTSTRAP=${ORIGIN}/fundamental.ini
 STARTLANG=



 Change the Logo=1 to Logo=0. Then save - remember if your on Windows 7 or Vista, you will have to save the document to somewhere else, eg the desktop, then copy it into the directory replacing it over the other one as Notepad does not have administrative rights.



So my bug is  basically that the logo is taking too long to load. I don't know what it is about that logo, but whatever it is, its causing significant extra time on the loading time of Libreoffice and I suspect OpenOffice, and that loading time is definitely a factor why many people will switch away from it.
Comment 1 weaselthatbites 2012-02-22 02:27:59 UTC
This has applied to all versions of Libreoffice, though my testing was done on 3.5 final.
Comment 2 Joel Madero 2012-10-16 22:58:51 UTC
I can confirm that it shaves off some time but my results are substantially less. My results

With logo: 18 seconds

Without Logo: 12 seconds

That's still about a 33% faster original boot.

I'm marking this as a minor bug, low priority. Rationale:

The 6 second shaving off is a one time ordeal, after you get your config folder set up (which is what is happening with first run of LibO), the time savings vanish for me (just about, maybe a 2/10ths of a second savings). Ultimately this has no impact on ability to make professional quality work and after running LibO 100 times might result in saving a minute or two of your time.

Interesting catch though, I'm curious to see what is happening different when logo runs.
Comment 3 Cor Nouws 2013-07-02 22:04:58 UTC
Hi Weasel,
Could you pls share your more recent experiences?
thanks,
Cor
Comment 4 weaselthatbites 2013-08-27 09:29:26 UTC
To Cor Nouws,

When I updated to version 4, the loading problem totally disappeared. Whatever magic you guys do, it seemed to have worked.

Thank you very much indeed. It now takes under 2 seconds to load with the logo on. 

For me, you can consider this bug closed. I don't know if other users also find the new version much better, but I do.

Once again many thanks,

Weasel123
Comment 5 Maxim Monastirsky 2014-06-18 13:55:15 UTC
(In reply to comment #4)
> For me, you can consider this bug closed.