Calc 24.8.1 vs. 24.2.6 three times slower

joshua4 · September 13, 2024, 8:53pm

I am experiencing a slowdown between 24.2.6 and 24.8.1. Any ideas?

I have a document that:

uses lots of formulas entered under Named Ranges
uses a largish UDF macro
is 49 sheets of about 250 rows and 25 columns each
uses external references to locally saved CSV files

I installed 7.6. Calculation time was 13 seconds. Uninstalled LO.
I installed 24.8.1. Calculation time was 53 seconds. Uninstalled LO.
I installed 24.2.6. Calculation time returned to 11 seconds.
Notice the order.

Save times and “Adapt row height” times are similarly affected.

If this does not seem to be a common experience, I can work to generate fake CSV data files and post the document.

The last speedy version seems to be:

Version: 24.2.6.2 (X86_64) / LibreOffice Community
Build ID: ef66aa7e36a1bb8e65bfbc63aba53045a14d0871
CPU threads: 20; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: threaded

My system:

OS Name	Microsoft Windows 11 Pro
Version	10.0.22631 Build 22631
Processor	12th Gen Intel(R) Core™ i7-12700, 2100 Mhz, 12 Core(s), 20 Logical Processor(s)
Installed Physical Memory (RAM)	64.0 GB

fpy · September 14, 2024, 5:37am

if you can narrow down to the exact version, it will definitely help;
https://wiki.documentfoundation.org/QA/Bibisect

otherwise, you may end up in a long standing thread like 158774 – Serious slowdown in recent Libreoffice calc release

joshua4 · September 14, 2024, 3:10pm

What do I use as the repository? Trying to clone into https://bibisect.libreoffice.org/bibisect-win64-24.8.git says does not exist.

fpy · September 14, 2024, 4:52pm

https://bibisect.libreoffice.org/win64-24.8

joshua4 · September 15, 2024, 8:26pm

Thank you. I can start master, and I can tag it as ‘latest’.
Then git checkout latest works fine and I can still start the latest as ‘latest’ or ‘master’ with instdir/program/soffice
But git bisect start latest oldest or git checkout oldest
returns error like

error: Your local changes to the following files would be overwritten by checkout:
        instdir/CREDITS.fodt
        instdir/LICENSE.html

Nonetheless, git log and git tag do show ‘oldest’ tagged as such.

mikekaganski · September 16, 2024, 4:34am

You didn’t need to tag it. When you need to checkout master, or start bisect and refer to that revision, you do it using the master name.
It’s unfortunate, that some of our bisect repositories have that problem of tracking files normally updated by operation of the program. You will have to run git restore . before each checkout operation (either manual checkout, or git bisect good/bad).