I have installed LO 3.4.3 on some very old PCs (P3, 500 MHz, 512 MB RAM) running Windows XP. When starting up, it takes about 1:20 minutes for the application to start. Once LO is up and running, it runs quite well. Even opening new documents via the quickstarter only takes seconds but is not an option (see Bug No. 41229 about that). We also tried to improve startup by disabling the JRE but this only brought us some 5 seconds (btw. Oracle JRE6_27 is installed). The system is very optimized so there are no unnecessary jobs running in the back. System memory is almost free after windows startup. Almost no hard disc activity can be seen while starting LO, but the job runs at 99% CPU. Only in the last 10 seconds you can hear the HDD work heavily but this might be because some binaries are loaded late. This makes me think that this is _not_ a problem of low memory and swapping (and even if the HDD activity was because of swapping, this would only explain the last 10-20 seconds of the slow startup). There must be some way to improve the startup procedure, maybe by offering an alternative setup that does not load so many extensions/tool/translations or similar additions. We only have these very old PCs because this is a ground school with no almost no budget for the pupils PCs. Also, I think many educational projects in developing or third world countries have a similar problem (very old hardware) and deserve a bearable fast launching office solution.
The same on a PowerMac G4 at 1350 MHz. Opening a odt text file takes as long as 20 sec., from clicking into the editing window till being able to type the first character takes another 5 sec. This cannot really be true… (-;
Obviously this problem is multiplatform/multi-OS.
[This is an automated message.] This bug was filed before the changes to Bugzilla on 2011-10-16. Thus it started right out as NEW without ever being explicitly confirmed. The bug is changed to state NEEDINFO for this reason. To move this bug from NEEDINFO back to NEW please check if the bug still persists with the 3.5.0 beta1 or beta2 prereleases. Details on how to test the 3.5.0 beta1 can be found at: http://wiki.documentfoundation.org/QA/BugHunting_Session_3.5.0.-1 more detail on this bulk operation: http://nabble.documentfoundation.org/RFC-Operation-Spamzilla-tp3607474p3607474.html
Dear bug submitter! Due to the fact, that there are a lot of NEEDINFO bugs with no answer within the last six months, we close all of these bugs. To keep this message short, more infos are available @ https://wiki.documentfoundation.org/QA/NeedinfoClosure#Statement Thanks for understanding and hopefully updating your bug, so that everything is prepared for developers to fix your problem. Yours! Florian
This is also an issue on WinXP, SP2 on a P4 2.8 GHz with 504 MB RAM. I started LO by clicking the "Libre Office" link (so no module is started directly) and measured the time. For the first 20 seconds nothing happend at all (no UI feedback). Then the spashscreen showed up and 6 seconds later the main menu for creating new documents was shown. The problem is, that the user does not notice the startup of the program for the first 20 seconds until the splash screen shows up. This is a corporate network setup, the software is deployed centralized. I will try and see if the newer versions are still affected and update this bug if it is still present.
(In reply to comment #8) > This is also an issue on WinXP, SP2 on a P4 2.8 GHz with 504 MB RAM. > > I started LO by clicking the "Libre Office" link (so no module is started > directly) and measured the time. > For the first 20 seconds nothing happend at all (no UI feedback). Then the > spashscreen showed up and 6 seconds later the main menu for creating new > documents was shown. > > The problem is, that the user does not notice the startup of the program for > the first 20 seconds until the splash screen shows up. > > This is a corporate network setup, the software is deployed centralized. I > will try and see if the newer versions are still affected and update this > bug if it is still present. Can you please try with the latest Fresh version and see of things have improved? Please note that during the first run LO is doing some added configuration steps that can make the start up appear long. After that it should start up quicker. That's the figure we'd be interested in.
Never independently confirmed by QA team - moving to UNCONFIRMED to make sure they see it. Thanks for your patience and understanding.
I send back this one to NEEDINFO waiting for update of the bug status with current LibO releases... anyway with such old and powerless equipment is probably not possible to achieve great performances... I wonder how MS Word behaves in the same computers.... (In reply to peter.schmidt from comment #0) > I have installed LO 3.4.3 on some very old PCs (P3, 500 MHz, 512 MB RAM) > running Windows XP. (In reply to peter.schmidt from comment #8) > This is also an issue on WinXP, SP2 on a P4 2.8 GHz with 504 MB RAM.
Actually moving this to NOTABUG - it's clearly a hardware issue. I can't reproduce on 4 machines that are newer. It's one thing to request that we continue supporting outdated hardware, it's another to expect for us to have great performance on these machines while continuing to improve all other areas of the project including filters, performance on newer machines, etc . . .