Description: Fileopen ODT: Opening of multiple files slower and more CPU hogging since LibO5.0 Steps to Reproduce: 1. Extract the attached zip 2. Open Writer 3. File -> Open -> Select all the files in the zip 4. Click open & monitor time & CPU usage Actual Results: LibO4.4.7.2 -> 12 seconds LibO6.2.0.0 -> 27 seconds Expected Results: Something like Libo4.4.7.2 Reproducible: Always User Profile Reset: No Additional Info: Version: 6.2.0.0.alpha0+ Build ID: 1b21ff86effe58ae368457de8fec654ba4c8edd9 CPU threads: 4; OS: Windows 6.3; UI render: default; TinderBox: Win-x86@42, Branch:master, Time: 2018-07-30_03:13:35 Locale: nl-NL (nl_NL); Calc: CL
Created attachment 143862 [details] Example file
hi Telesto, did you try the same with different extensions like .DOC or .DOCX? is the performance regressione affecting all extensions or is limited to .ODT?
In reply to tommy27 from comment #2) > hi Telesto, did you try the same with different extensions like .DOC or > .DOCX? > is the performance regressione affecting all extensions or is limited to > .ODT? I forgot to check. But yes, it's limited to ODT (checked against doc/docx)
I don't have 4.4. on Linux, but I got 23 secs with 6.2. On Win 10, I got 16 secs with 6.2 and 4.4.7. Thus I am not confirming this.
Hi Telesto, Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ?
Dear Telesto, This bug has been in NEEDINFO status with no change for at least 6 months. Please provide the requested information as soon as possible and mark the bug as UNCONFIRMED. Due to regular bug tracker maintenance, if the bug is still in NEEDINFO status with no change in 30 days the QA team will close the bug as INSUFFICIENTDATA due to lack of needed information. For more information about our NEEDINFO policy please read the wiki located here: https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO If you have already provided the requested information, please mark the bug as UNCONFIRMED so that the QA team knows that the bug is ready to be confirmed. Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-NeedInfo-Ping
I still reproduce Version: 6.3.0.0.alpha0+ Build ID: 91b2239783dc716bd71ce7962bfd7e341dfe4175 CPU threads: 4; OS: Windows 6.3; UI render: default; VCL: win; TinderBox: Win-x86@42, Branch:master, Time: 2019-05-08_09:49:32 Locale: nl-NL (nl_NL); UI-Language: en-US Calc: threaded Difference maybe a little smaller.. performance of 4.4.7.2 is slightly worse, but say 6 seconds or so.. Slightly off topic and maybe not an objective comparison, but LibO 6.3. opens the DOC format of the same bunch of files substantial faster, ~10 seconds compared to ~25 when saved as odt
Telesto, perhaps there is further impriovement with the actual master build. Could you please try to reproduce it with a master build from http://dev-builds.libreoffice.org/daily/master/ ? => NEEDINFO
Dear Telesto, 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 MassPing-NeedInfo-FollowUp