I experienced a very similar problem like described in bug ID 63640, however with Calc.
I use a huge spreadsheet: about 50 sheets, each around 1000 rows long, with many calculating and searching formulas like VLOOKUP and HLOOKUP, in xls format it takes over 80Mb. I use it for data collection with my collegues, on several computers (of course not simultaneously). It was originally created in MS Excel 97, but after some time I tried to use it in LibreOffice 3.6.5 and every version thereafter. It is opened finely, every cell looking okay, however opening from a local HDD takes at least 7-8 minutes, while saving it in either ods or xls format takes more than 15 minutes (slow progress bar when opening, no progress bar visible during saving)!
Just to compare, MS Excel 97 opens the same file in about 10-15 seconds, on a quite similarly built hardware and OS.
This saving problem may cause another also reported bug, namely that it seems to freeze the program for similarly long time during editing if autosaving is set on (without any progress bar at the bottom), and this freezing disappears after changing settings. Now I can at least edit the file if I'm patient enough, however opening and regular saving takes same long as before. When trying to use LibreOffice for my regular work with spreadsheets like this, it is a huge limitation, I would call it a major problem!
I use WinXP system.
To do anything about this problem we need a test file showing the issue. Without test files it is impossible to work on performance problems.
Marking as NEEDINFO, get us a test case and set to UNCONFIRMED and we will investigate
Created attachment 78289 [details]
Loading on my Macbook Pro to around 3-4 min I don't think this is to long because the file is very big. Wen trying to open with Apple Number it crasht
opening the file toke 1GB of my ram
saving the file into .xls format toke 3-4 mintis BUT it toke 99,9% of my CPU and !,5 GB of ram! So if some one has a les powerfull CPU or less ram it will take way longer.
Build ID: fd179c5f308a0a611bc2b5a479e28ff3ced7964 (21 apr)
os: mac osx 10.8.3
system: macbook Pro
cpu: 2.5 GHZ in core I5
I tried to save the test file to an external HDD. During all the so called saving process, the outside HDD only worked in the last 1-2 seconds. All other work is done in the memory before writing any byte to the file.
I'm not a C++ expert so I don't understand much from the source code, however I write programs in Delphi and experienced similar problems when working with automatically refreshing data: huge refresh-loops launched when a new item is added to the database to be refreshed. Probably something similar is happening here, since the sample database has many formulas. If their values are recalculated every time a new cell is added (or changed) during loading, it might cause severe speed problems and huge memory usage exponentially related to the amount of formulas. However it does not have any sense to do a cell-value refreshing before saving.
Maybe it would be worth if somebody who is somewhat experienced in editing LibOffice code to check that out. If that's the problem, I would have some general ideas how to make cell-value refreshing (and thus loading) way faster. However I would need someone knowing C++ language to set it into practice...
A potentially helpful new finding with the same file:
If autosave is switched on, it is faster compared to clicking the save button. However the progress bar behaves weird: it progresses to about 90% quite normally, then it goes back and forth between 90 and 95%, then progresses to between 95 and 98%, going back and forth again in this range, then progressing to 99%, where I see no "going-back-and-forth", however I cannot exclude that, since the progress bar waits for several minutes in this position right at the right border of my screen. It seems as if somewhat would be performed several times at the end of the saving process, slowing it down quite a lot.
I'm using LO 4.0.2 shipped with Ubuntu 13.04.
I don't have any problem opening the attached file with 107 sheets. It opened in less than 2 minutes.
Laptop: Acer Travelmate 4740
OS: Ubuntu 13.04
(In reply to comment #7)
> I'm using LO 4.0.2 shipped with Ubuntu 13.04.
> I don't have any problem opening the attached file with 107 sheets. It
> opened in less than 2 minutes.
When I saved this sample file in .ods format I observed the issue from comment 6 (which I have also seen in my large files): The progress bar goes to around 90% quickly, flutter around for a while, then goes to about 98%, stays unchanged for a long time, then vanishes.
It's also worth noting that there is a period of time between when the progress bar vanishes and calc is usable after the save. It appears there is some processing happening after the progress bar vanishes that should be covered by the progress bar.
A logging feature that records the state of the save with every progress bar change could:
1) Provide information to produce a smoother progress bar display, which would make it less likely for users to think that calc has hung. The fluttering, pause at 98%, and the unresponsive period after the bar vanishes are all worrisome as a user.
2) Give some hints about which parts of the save are unexpectedly slow (from the view of the original progress bar implementer) and might suggest areas to consider for performance improvements.
Adding self to CC if not already on
Migrating Whiteboard tags to Keywords: (perf)
Created attachment 121301 [details]
Another for test
I can confirm this issue with another with one sheet but of about 25000 rows from Excel also converted in ODS on 5.0.3 with Linux Debian 8 and Ubuntu 14.
The loading or closing is very slow. Some edit operation also. Another issue is a big needing of memory to 2.5 GB (from top) after some operations than reduce never until close LibreOffice. CPU activities were high or huge.
I can comfirm this and I would add that Calc in general is much much slower than Excel.
1. open attached "big_file.ods"
2. hold down control and use the mouse wheel to zoom in and out
3. select all
4. apply a command
5. double click to enter a single cell
7. close and reopen
all of these operations take much MUCH longer than Excel and sometime give the appearance of a crash or lock the program into a state where in continually scrolls in one direction or the other, taking up to 30 seconds to return control to the user.
Created attachment 133938 [details]
file to demonstrate the extreme slowness of this program versus Excel
I had expected Calc, being newer and less corporate, to be less bloated, have a smaller footprint and perform better than Excel. It's the opposite.
Calc 126.96.36.199 release is significantly slower to open, edit and save than Calc 188.8.131.52 for the exact same spreadsheet. Calc 184.108.40.206 also can't open some files that Calc 220.127.116.11 can easily open. Calc 18.104.22.168 will crash on very large sheets and show an Allocation failed error dialog on some of the large spreadsheets that the older version will easily open.
The spreadsheets I use do have a lot of data in them. Only 1 sheet but greater than 60,000 rows in 6 columns. And 3 charts showing 1 column of data each.
I would look at what was added between Calc 22.214.171.124 and Calc 126.96.36.199 to see what code causes the 188.8.131.52 to be so slow that it is unusable.
(In reply to mitchfx from comment #15)
> The spreadsheets I use do have a lot of data in them. Only 1 sheet but
> greater than 60,000 rows in 6 columns. And 3 charts showing 1 column of data
> I would look at what was added between Calc 184.108.40.206 and Calc 220.127.116.11 to see
> what code causes the 18.104.22.168 to be so slow that it is unusable.
Please open a new bug report with a sample spreadsheet.
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
The issue seems to be fixed for me.
Tested on Version: 22.214.171.124
Build ID: efb621ed25068d70781dc026f7e9c5187a4decd1
Threads CPU : 2; OS : Linux 4.9; UI Render : par défaut; VCL: gtk2;
Locale : fr-FR (fr_FR.utf8); Calc: group threaded