Bug 68025 - FILEOPEN: poor performance when open xslx files
Summary: FILEOPEN: poor performance when open xslx files
Status: RESOLVED INVALID
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.1.0.4 release
Hardware: Other Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard: BSA
Keywords:
Depends on:
Blocks:
 
Reported: 2013-08-12 14:28 UTC by altezna
Modified: 2014-07-08 17:17 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
sample document (1.89 MB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2013-08-12 14:28 UTC, altezna
Details

Note You need to log in before you can comment on or make changes to this bug.
Description altezna 2013-08-12 14:28:48 UTC
Created attachment 83971 [details]
sample document

Problem description: 
slow opening and saving performance even saved as native odf format

Steps to reproduce:
1. open the attached xlsx file (a)
2. save (a) as xlsx (b)
3. save (a) as odf (c)
4. open the odf (c)
5. save (c) as odf (d)

Current behavior:
open original xlsx (a) 7s
save xlsx (a) as xlsx (b) 23s
open resaved xlsx (b) 11s
save xlsx (a) as ods (c) 12s
open converted ods (c) 16s
save ods (c) as ods (d) 3s
open resaved ods (d) 16s

All operations in Excel 2013 were done in 2 seconds except saving as ods took 5 seconds.

Expected behavior:
Open operation should be done within less than 2 seconds.
Operating System: Windows 8
Version: 4.1.0.4 release
Comment 1 Jean-Baptiste Faure 2013-09-14 13:51:06 UTC
I do not reproduce under Ubuntu 13.04 x86-64 with LO 4.1.3.0.0+. When saving under whatever format, I do not have time to see the progress bar. Opening the file is about 4 or 5 seconds

Performance improvement is a perpetual work in progress, so could you update to the current stable version 4.1.1 and try again?

Best regards. JBF
Comment 2 altezna 2013-10-04 15:05:56 UTC
With 4.1.1.2, I see improvement on opening speed of those resaved odf files, (c) and (d), from 16s to 10s. Others are the same.
Comment 3 Jean-Baptiste Faure 2013-11-13 20:17:35 UTC
Rewording of the summary.

Did you have spellchecker enabled during your tests ?

Best regards. JBF
Comment 4 Maxim Monastirsky 2013-11-13 20:46:12 UTC
Maybe Windows 8 specific - Please see Bug 68821. I also had some serious performance issues under Windows 8 with opening and saving files, but now I don't have Windows 8 anymore so I can't test it.
Comment 5 QA Administrators 2014-06-01 21:29:49 UTC
Dear Bug Submitter,

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 INVALID due to lack of needed information.

For more information about our NEEDINFO policy please read the wiki located here: 
https://wiki.documentfoundation.org/QA/FDO/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
Comment 6 QA Administrators 2014-07-08 17:17:38 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INVALID 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 FDO