Summary: | FILEOPEN: Worse-than Linear Performance Degradation Opening Change-Tracked ODTs | ||
---|---|---|---|
Product: | LibreOffice | Reporter: | orcmid <dennis.hamilton> |
Component: | Writer | Assignee: | Not Assigned <libreoffice-bugs> |
Status: | NEW --- | ||
Severity: | normal | CC: | ahiijny, aron.budea, dennis.hamilton, kelemeng, michael.stahl, noelgrandin, sebastian |
Priority: | medium | Keywords: | perf |
Version: | 3.5.3 release | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | BSA | ||
Crash report or crash signature: | Regression By: | ||
Bug Depends on: | |||
Bug Blocks: | 83946 | ||
Attachments: |
Spreadsheet of Timing Tests showing degradation with document growth
Additional Test Result |
Description
orcmid
2012-05-12 11:45:00 UTC
SPREADSHEET DETAILS THIS ODF SPREADSHEET provides more data points with regard to the timings and the different configurations and software releases tested. Different releases of LibreOffice are employed, depending on what was handy for testing with different platforms. When available, I provide timing tests with OpenOffice.org 3.3.0 as well. This is to provide a baseline and confimr that the problem has existed since at least that releast of OpenOffice.org. NOTE: THE MEASURED TIMINGS ARE NOT SUITABLE FOR COMPARISONS BETWEEN PRODUCTS. These timings were determined manually with a stop watch. The conditions were not carefully controlled and the typical variances related to configuration differences, background activity, and system state are too high. The sole purpose of the timings is to demonstrate that the degradation of performance is consistent and predictable across all OpenOffice- lineage software. The variance between releases is negligible compared to the major source of degradation. CONFIGURATIONS Astraendo is a Dell XPS 9100 with Windows 7 en_US x64, 18GB RAM, and an Intel i7-980x 3.33GHz 6-core processor. Quadro is a Toshiba Satellite Tablet PC with Windows XP SP3, 1.5GM RAM, and an Intel Pentium M (Celeron) 1.7GHz processor. VVM is Vista Ultimate en_US x86 running in Virtual PC on Astraendo Win8CP64 is Windows 8 Customer Preview en_US x64 running in VirtualBox on Astraendo Zorin Core is Zorin OS (Core, Debian/Ubuntu) x64 running in VirtualBox on Astraendo Zorin Edu is Zorin OS (Edu, Debian/Ubunto) x86 running in VirtualBox on Astraendo SPECIAL CASES Package releases are those provided in a distribution. These are not from LibreOffice download sites and apparently there are odd failure cases with those. Open Fail means that the document went through all of the slow opening process and when it appeared to be ending, the application simply closed without the document ever being shown. Close crash means that there was a crash on closing the document in the application, with a report that the software had not closed properly and work might have been lost. The document was fine (it had not been touched) but the lock file was still present in the file system. This defect is apparently in common code inherited from OpenOffice.org in both LibreOffice and Apache OpenOffice: https://issues.apache.org/ooo/show_bug.cgi?id=119341 It appears that symptoms of this problem have been identified as far back as OpenOffice.org 1.0: https://issues.apache.org/ooo/show_bug.cgi?id=29842 There are potentially multiple defects behind these, ones related to change-tracking on open (as well as autosave and save but not quite as slow) and to bloating of the .ODT file for no apparent reason. All of the ODF Text documents, WD03a, ..., WD04a were produced with LibreOffice 3.3.2, the software being used for an ODF maintenance activity (no changes to the software are made during the project to avoid regressions). The original document with which editing began is the ODF Text for the OASIS OpenDocument Format 1.1 Standard. This document was produced by generator "StarOffice/8$Solaris_Sparc OpenOffice.org_project/680m5$Build-9114". the change tracking implementation in Writer is and always has been embarrassing, nothing new here. SwDoc::AppendRedline is at least O(n^2), perhaps worse (fortunately i haven't looked at it lately). file import isn't actually the worst performance problem; finding that is easy, just grep for //JP 06.01.98: MUSS noch optimiert werden!!! ** 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 on a currently supported version of LibreOffice (4.3.5 or later): https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) Thank you for your help! -- The LibreOffice QA Team Created attachment 111796 [details] Additional Test Result (In reply to QA Administrators from comment #4) [ ... ] > If the bug is present, please leave a comment that includes the version of > LibreOffice and your operating system, and any changes you see in the bug > behavior [ ... ] The bug remains present. Machine: Dell XPS with Windows 8.1 Professional LibreOffice: 4.3.5.2 In this comparison, the times seem longer than previously but the key is that the non-linearity has not changed. The different in timings may be because of differences in configuration and the absence of controlled timing, so these should not be viewed as absolute comparisons. The new attachment is an ODS file that adds the test runs just made. ** 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 on a currently supported version of LibreOffice (5.1.6 or 5.2.3 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) 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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20161108 This looks much better in bibisect-7.2, yet the basic pattern is still here. Measuring on my not-so-new work laptop of Win10 i5-4310M @2.7Ghz with time OOO_EXIT_POST_STARTUP=1 instdir/program/swriter.exe $example.odt I got the following values (as a rough average of 3 consecutive measurements). For comparison I copied values from the first attachment here: WD03a WD03b WD03c WD04a WD03x LO 7.2 00:12 00:25 01:31 02:26 00:11 Astraendo 3.3.2 10s 2m29s 10m09s 15m40s 9s @Noel: this may interest you... Dear orcmid, 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 |