Description: Calculating optimal width relatively slow CPU/consuming Steps to Reproduce: 1. Open the attached file 2. Select column A 3. Expand the toolbar button column & click optimal width (takes 5-10 seconds) Actual Results: It takes 5- 10 seconds on a column of data Expected Results: It must be possible to do this bit faster Reproducible: Always User Profile Reset: No Additional Info: Version: 7.0.0.0.alpha0+ (x64) Build ID: 4501a0ba623ad61c5a4e0b807da2e96f0e4ce82c CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win; Locale: nl-NL (nl_NL); UI-Language: en-US Calc: CL
Created attachment 159222 [details] Example file
takes 6 seconds for me Version: 7.0.0.0.alpha1+ Build ID: 1ffe59ef31186e36ad0aa7bbcdd32e407ee8d26c CPU threads: 4; OS: Linux 4.19; UI render: default; VCL: gtk3; Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded could you please add your measurements ? 5-10 seconds doesn't seems precise to me
8 Seconds with 7.0 3 seconds with 4.0.0.3
No repro on Linux, but yes on Windows Bibisected with 6.3 to https://git.libreoffice.org/core/commit/b7ddc514bff9bdf682abae537f990aa01dc2c0fb Upgrade to latest HarfBuzz 2.3.1 So the same effects as bug 131909
Dear Telesto, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
According to : https://wiki.documentfoundation.org/QA/GetInvolved I retested it. It's now 3.5 seconds. Not perfect, but seems better :-/ version : Version: 7.3.2.2 (x64) / LibreOffice Community Build ID: 49f2b1bff42cfccbd8f788c8dc32c1c309559be0 CPU threads: 24; OS: Windows 10.0 Build 19044; UI render: Skia/Vulkan; VCL: win Locale: fr-FR (fr_FR); UI: fr-FR Calc: CL
I get these on Windows 10 7.0 bibisect repo, oldest: 22.7 secs (same result with 7.1 repo newest) 7.5: 3.8 secs so it seems like quite an improvement.
seems resolved based on comment 3 + comment 6
Yeah, let's close. Many Calc optimisations have been made in the two years since this was reported and more will surely follow.