On 10/26/05, Anthony Chilco <[EMAIL PROTECTED]> wrote: > Hi Bryce, Jim, > The reason for the long load and save times is that all OOo files are > stored in XML format. Basically, they're text files and must be parsed > and translated to binary each time. MSO saves only in binary format, so > the load time is shorter. The only way around it is to break your file > up into more manageable sections if that's possible, and link the output > of each section into one file. > tc
This is NOT the problem. I downloaded the file linked in the issue I referenced, opened it in excel, deleted all the charts (which were mentioned as possible culprits in the issue comments), re-saved the xls, and also saved it as xml. The result was a very large file that excel 2003 took 1:25 CPU time to open, as opposed to 0:05 CPU time to open the xls. It also took excel 0:27 CPU to save a new copy of the xml version, as opposed to 0:02 to save the xls version. OpenOffice on the other hand, while trying to open the original xls, used up all of my physical memory (~300MB was free before starting), then slowed to a crawl when it started into my page file (assumedly), ballooned to around ~350MB memory usage, and I gave up and killed the process after it had been trying to open it for almost 10 minutes and only showed about 50% progress. OpenOffice's performance on an xls version is at least an order of magnitude worse than excel's performance on an xml version. I'm trying to get work done here, so I can't even devote the 1/2-hour it would take to get the xls version open and try to save a more native ods version. -- Bryce Schober --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
