Date: prev next · Thread: first prev next last
2010 Archives by date, by thread · List index



Here is a table of loading times (in seconds)
This test was carried out under Windows XP SP3 with the 300.000 lines sample
I mentioned in a previous post, converted to the 4 formats.
http://www.openoffice.org/nonav/issues/showattachment.cgi/66356/300000_line_sample.xlsx


http://nabble.documentfoundation.org/file/n2006665/Loading_times.png 

(NOTES: * LO/OOo only loads CSV files after a screen asking for
encoding/delimiters; ** I'm not surprised that MS doesn't support .gnumeric
but I think LO/OOo should)

Notice that LO/OOo takes 4 times longer to load an ODS file than Gnumeric
and 24(!!!) times longer to load the xlsx file than Excel and Gnumeric.

Interestingly, ODS is also the slowest format to load in Gnumeric.

These results show that some optimization is needed for both LO/OOo and the
ODS format...

(Loading ODS in Office 2007 used the latest version of the OpenXML/ODF
Translator Add-in for Office http://sourceforge.net/projects/odf-converter/.
No comments on the loading time :) )

-- 
View this message in context: 
http://nabble.documentfoundation.org/Why-is-LO-OOo-so-slow-loading-a-spreadsheet-tp2006665p2006665.html
Sent from the Discuss mailing list archive at Nabble.com.


-- 
Unsubscribe instructions: E-mail to discuss+help@documentfoundation.org
Archive: http://www.documentfoundation.org/lists/discuss/
*** All posts to this list are publicly archived for eternity ***

Context


Privacy Policy | Impressum (Legal Info) | Copyright information: Unless otherwise specified, all text and images on this website are licensed under the Creative Commons Attribution-Share Alike 3.0 License. This does not include the source code of LibreOffice, which is licensed under the Mozilla Public License (MPLv2). "LibreOffice" and "The Document Foundation" are registered trademarks of their corresponding registered owners or are in actual use as trademarks in one or more countries. Their respective logos and icons are also subject to international copyright laws. Use thereof is explained in our trademark policy.