On Tue, Feb 12, 2013 at 6:47 PM, Andrew Douglas Pitonyak <and...@pitonyak.org> wrote: > > If you have a good setup for testing such things, try loading, saving, and > closing AndrewMacro.odt >
That's a big one: Release the Kraken! The time to close the document (not saving) could be low-hanging fruit. Presumably there is a free of a huge data structure to reclaim the heap. It would be interesting to see how many times we call free. When we had a similar problem in SmartSuite (many years ago) we solved it by using a custom memory allocator (overriding operator new). For allocations we managed our own heap, keeping related data structures together. I don't know if it is still a benefit today, but back then "locality of reference" was a big thing when it came to memory paging and caching. In any case when it came time to free the document, we did it trivially. Instead of doing the zillion free's to clean up the document data structures we called the global delete operator on the entire memory buffer, cleaning it up in a single call. The downside was this confused any tooks we used to look for memory leaks. Most of them looked at heap-level allocations and frees and reported a mismatch. So we had a debug version of the library as well, that was slower but did the memory management more traditionally. And we used the faster version for QA and production. -Rob > LO claims that much of their improvements are related to large Calc > documents. Might be nice to find and test their large test Calc document... > Not sure what they used, however. > > > On 02/12/2013 07:42 AM, Rob Weir wrote: >> >> I did some tests to see how we were doing, comparing AOO 3.4.1 on >> Windows against OOo 3.3.0. And since LibreOffice claims that their >> 4.0 release is much faster and leaner, I tested them as well, to see >> if we could learn anything. >> >> I just did a basic test, seeing how long it took to load a large text >> document, in this case the ODF 1.2 specification. I looked at memory >> consumed and the number of seconds to load. I loaded the document >> once to reduce the impact of disk caching and then repeated 5 times >> and took the average. All tests done on identical hardware. >> >> Memory use (KB for soffice.bin): >> >> OOo 3.3.0: 133,472 >> AOO 3.4.1: 129,928 >> LO 4.0: 165,796 >> >> Load time for ODF 1.2 specification (seconds, average of 5 loads) >> >> OOo 3.3.0: 16.0 >> AOO 3.4.1: 20.9 >> LO 4.0: 23.7 >> >> >> Does anyone have any other good test documents for doing performance >> tests of OpenOffice? >> >> Regards, >> >> -Rob >> > > -- > Andrew Pitonyak > My Macro Document: http://www.pitonyak.org/AndrewMacro.odt > Info: http://www.pitonyak.org/oo.php >
