Bug 78067 - Poor ODP save caused by swapping in all images (pointlessly)
Summary: Poor ODP save caused by swapping in all images (pointlessly)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Libreoffice (show other bugs)
Version: 4.2.0.0.alpha0+ Master
Hardware: Other All
: medium critical
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on: 47148
Blocks:
  Show dependency treegraph
 
Reported: 2014-04-29 08:45 UTC by Michael Meeks
Modified: 2014-05-24 20:55 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments
export- showing a ton of reading of images (but no writing) (376.25 KB, image/png)
2014-04-29 08:45 UTC, Michael Meeks
Details

Description Michael Meeks 2014-04-29 08:45:07 UTC
It takes me a very long time to save my 88 slide deck (much longer than to load it) - you can load it as hybrid PDF here:

http://people.gnome.org/~michael/data/2014-04-26-story-of-libreoffice.pdf

Profiling it in callgrind overnight (yes it takes that long ;-) it turns out that ~all of that time is consumed -loading- and de-compressing the images - there is ~zero cost for exporting them (so I can only think that the binary data is copied directly across to the new container - which is good).

That is really silly =) and (perhaps) another example of the really unfortunate image handling design we have [ though it could just be a silly bug I guess ].
Comment 1 Michael Meeks 2014-04-29 08:45:49 UTC
Created attachment 98165 [details]
export- showing a ton of reading of images (but no writing)
Comment 2 Michael Meeks 2014-05-24 20:55:45 UTC
Interestingly the slowest conversion in our callgrind tests at:

http://dev-builds.libreoffice.org/callgrind_report/

is 051_fdo#73300.odt-convert - whose profile shows a huge amount of time spend loading, un-compressing and checksumming images - but virtually no time converting/exporting them. Which is perhaps another interesting data point.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.