Bug 137598 - impress open pptx file with 200 slides is slower then MS Office
Summary: impress open pptx file with 200 slides is slower then MS Office
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Impress (show other bugs)
Version:
(earliest affected)
7.0.2.2 release
Hardware: x86-64 (AMD64) All
: lowest minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:pptx, perf
Depends on:
Blocks: PPTX
  Show dependency treegraph
 
Reported: 2020-10-19 16:08 UTC by meilin
Modified: 2023-01-22 03:28 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
pptx file test case (413.95 KB, application/vnd.openxmlformats-officedocument.presentationml.presentation)
2020-10-19 16:11 UTC, meilin
Details

Note You need to log in before you can comment on or make changes to this bug.
Description meilin 2020-10-19 16:08:45 UTC
Description:
impress open pptx (200 slides) file use 5 seconds, but when i use MS Office open this pptx file, it use about 2 seconds.

Steps to Reproduce:
1.use impress open pptx file
2.use MS Office open pptx file 
3.

Actual Results:
impress open pptx file (200 slides) use 5 seconds, but when i use MS Office open this pptx file, it use about 2 seconds.

Expected Results:
impress open pptx file (200 slides) use about 2 seconds.


Reproducible: Always


User Profile Reset: No



Additional Info:
We take a look at the code, and we think, maybe, instead
of importing the document slide by slide, would it be possible to import all the slides at once with multiple threads
Comment 1 meilin 2020-10-19 16:11:06 UTC
Created attachment 166517 [details]
pptx file test case
Comment 2 Roman Kuznetsov 2020-10-19 19:55:23 UTC
I confirm a difference between PP with 2 and Impress with 5 sec

but I think it should be more a developer decision and I saw a discussion in a dev mail list. 
http://document-foundation-mail-archive.969070.n3.nabble.com/Optimization-thought-concurrent-importing-of-slides-td4289530.html

Let's wait..
Comment 3 Roman Kuznetsov 2021-01-21 12:04:50 UTC
Let's set it to NEW but with lowest minor importance
Comment 4 QA Administrators 2023-01-22 03:28:30 UTC
Dear meilin,

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