Bug 133085 - Calc is very very slow compared to MS Office - EDITING, FILEOPEN, FILESAVE
Summary: Calc is very very slow compared to MS Office - EDITING, FILEOPEN, FILESAVE
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
Keywords: filter:xlsx, perf
Depends on:
Blocks: XLSX File-Opening
  Show dependency treegraph
Reported: 2020-05-16 11:21 UTC by Khaldoun
Modified: 2022-04-01 03:40 UTC (History)
5 users (show)

See Also:
Crash report or crash signature:

Flamegraph (gen rendering) (631.84 KB, application/x-bzip)
2020-05-16 14:22 UTC, Julien Nabet

Note You need to log in before you can comment on or make changes to this bug.
Description Khaldoun 2020-05-16 11:21:54 UTC

When I open the file in LibreOffice Calc, whether as ODS or XLSX it hangs up when opening and I need to wait while it is frozen.

Then when I want to change the sheet to another, it simply hangs and I need to wait for so long again.

Saving the file is a nightmare as it hangs to the point that sometimes I need to kill the LibreOffice Calc or simply restart.

I really hate to say this, but when I use MS Office 2019 Pro Plus 64Bit, it just opens, asks to update from linked sources, I answer yes, in a wink it updates, then it all works super convenient. Saving the document is as fast as everything else with MS Office Excel.

Good to know:

I use LibreOffice

LibreOffice runs on Solus Linux 4.1

The file reads from 3 linked source files of data.

The file has many calculations in each row.

The file has almost 1,000 rows.

I tried to create the file in ODS format, the same result.
Create it in XLSX format, again the same.

I tried to have the source files as ODS and then XLSX still the same.

Until this problem is solved, I switched to Excel as I cannot afford the loss of time.

My PC specs:

Intel® Core™ i7-8550U CPU @ 1.80GHz × 8 CPU
SSD 256 GB Drive
Intel® UHD Graphics 620 (Kabylake GT2) GPU

I am ready to test any configuration, send more info, or try alpha or beta releases.

Thanks for a great product.


Steps to Reproduce:
1. Download the ZIP file with Main file and Data sources files. All files are in XLSX format.

ZIP File link: xyz

2. Place all files: Sub-All.xlsx, Ren-All.xlsx, Unsub-All.xlsx, and "Main.xlsx" in the same folder.

3. Open the "Main.xlsx" file in Calc.

4. Wait until the file is opened, then try to work on it.

Actual Results:
The file is very very slow and it is actually not usable.

Expected Results:
The file should open quickly and perform normally.

Reproducible: Always

User Profile Reset: No

Additional Info:
The file should load fast. Hate to see Excel doing better and be forced to use it instead of LibreOffice.
Comment 1 Julien Nabet 2020-05-16 11:34:38 UTC
Please give a try to 6.4.3.
If you still reproduce this, please attach an example file sanitized (see https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission)

Finally, you must know that if there are a lot of comments, it will slow down LO. This point needs a big refactoring.
Comment 2 Khaldoun 2020-05-16 12:00:59 UTC
The files are located in Google Drive at:


This is the main file and the 3 linked source files. They should be in the same folder. I am sure you can figure it out if need to fix the links.... let me know if any furthter details are needed.
Comment 3 Khaldoun 2020-05-16 12:03:28 UTC Comment hidden (obsolete)
Comment 4 Khaldoun 2020-05-16 12:07:08 UTC Comment hidden (obsolete)
Comment 5 Julien Nabet 2020-05-16 12:34:32 UTC
(In reply to Khaldoun from comment #3)
> Hello, I appreciate to confirm when the file is downloaded in order to close
> the share link to the file.

Zip file retrieved.

On pc Debian x86-64 with master sources updated today, I confirm it's long to just open Main.xlsx file
Comment 6 Khaldoun 2020-05-16 12:52:22 UTC Comment hidden (obsolete)
Comment 7 m_a_riosv 2020-05-16 13:05:43 UTC
Version: (x64)
Build ID: 30356cdb3581bc9e9118ef3dd2f3162d9256c3b6
CPU threads: 4; OS: Windows 10.0 Build 19608; UI render: Skia/Raster; VCL: win; 
Locale: es-ES (es_ES); UI: en-US Calc: CL

Half a minute to open Main.
But there are a couple of linked files not available.
Lot of formulas with VLOOKUP on linked files.
45 charts.

For me takes to much show the charts when selecting one or going to their sheet.
Comment 8 Julien Nabet 2020-05-16 14:22:17 UTC
Created attachment 160893 [details]
Flamegraph (gen rendering)

Here's a Flamegraph retrieved on pc Debian x86-64 with master sources updated today + gen rendering.
Comment 9 Julien Nabet 2020-05-16 14:25:30 UTC
Noel: thought you might be interested in this one. It's about slowliness for opening xlsx file and not related to comments.
I attached a Flamegraph.
Also, I used gen rendering to avoid all accessibility stuff with gtk3.

If needed, I can attach other Flamegraph in order to:
- test a patch
- test another action delay (when switching between sheets, save as another file...)
Comment 10 Khaldoun 2020-05-17 00:09:13 UTC Comment hidden (obsolete)
Comment 11 Khaldoun 2020-05-17 00:11:09 UTC Comment hidden (obsolete)
Comment 12 Khaldoun 2020-05-17 00:11:44 UTC Comment hidden (obsolete)
Comment 13 Khaldoun 2020-05-17 00:17:51 UTC Comment hidden (obsolete)
Comment 14 Khaldoun 2020-05-20 20:27:00 UTC Comment hidden (obsolete)
Comment 15 Khaldoun 2020-06-03 21:14:24 UTC Comment hidden (no-value)
Comment 16 Buovjaga 2021-05-03 12:14:31 UTC
This is a problematic report because the test file is not publicly available like it should be. If you can't share it as-is, then anonymise it and verify the problem still exists: https://wiki.documentfoundation.org/QA/Bugzilla/Sanitizing_Files_Before_Submission#Sanitize_file_text
Comment 17 Khaldoun 2021-05-07 23:21:57 UTC

Thanks for the feedback.. 

Yes, I agree it is a problematic report. But this is the only reason to have Windows+Office on my machine! I believe this can be the situation for many many more people.


- Will work on setting up an anonymized copy.
- Also, because the main file is reading from other source data files, then placing the files in a wrong way can make the reported issue irreproducable.

Given the file is very slow, arranging for an anonymized version is going to take some time. Not less than a week.

Also, to make sure the main file reads properly from the linked data files, I need to know your system (or the system of the person who will work on this). Is it Windows? Linux? Mac?

This issue is the only reason I still have Windows+Office on my machine!

Looking for your reply

Comment 18 Khaldoun 2021-05-07 23:23:46 UTC Comment hidden (obsolete)
Comment 19 Buovjaga 2021-05-08 05:36:26 UTC
(In reply to Khaldoun from comment #17)
> Also, to make sure the main file reads properly from the linked data files,
> I need to know your system (or the system of the person who will work on
> this). Is it Windows? Linux? Mac?

You don't need to worry about this detail :) Thanks for considering the anonymisation. If you want to confirm every important bit of info is cleaned, you can email the files to me before making them public.
Comment 20 Khaldoun 2021-07-24 19:29:51 UTC
Just updating that this issue is still there as I tested the same file on
Comment 21 Julien Nabet 2021-07-24 21:44:42 UTC Comment hidden (obsolete)
Comment 22 m_a_riosv 2021-07-25 16:33:26 UTC
If I'm not wrong, there is no sample file to test with.
Comment 23 Timur 2021-09-01 13:28:57 UTC
I set Needinfo for anonymized file from reporter or Julien.
Comment 24 QA Administrators 2022-03-01 03:42:48 UTC Comment hidden (obsolete)
Comment 25 QA Administrators 2022-04-01 03:40:30 UTC
Dear Khaldoun,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team