The performance project
This wiki page is the collaboration entry point for the OOo Performance project.
For questions and discussions, please use the new mailing list from the performance project: firstname.lastname@example.org
When you plan to file an issue with regard to performance, please make sure to add the keyword performance
The official (incubator) project was started February 2009, but there have already been a lot of activities in this area in the past, so some of the information here (especially on the linked wiki pages) might be outdated.
This page will be cleaned up soon.
Probably a lot - please continue here.
User Experience Index (UEI)
Helpful Tooling and Resources
Popular reference configuration(use similar env on Hamburg and Beijing)
CPU: Core2 Duo 1.5~2G Memory: 512M OS: WindowsXP HOME
Test & Tuning Tools
- Linux/cold-start simulator
- relocstat - dump relocation data
- RTL_LOGFILE - export RTL_LOGFILE=/tmp/foo
- valgrind - debug / trace memory usage
- callgrind - call graph profiler
- speedprof - a quick / hackish sampling full-stack-trace profiler & visualisation tool
- APPR - a performance regression tool suite
- Performance Related Test Documents
- TrueTime - profiler for windows, commercial product
Benchmarks & Description
If you have some benchmarks, share them here!
- The Fastest OpenOffice.org Edition comparison of four 2.4.1 editions on Fedora 9
- Is OpenOffice.org Getting Faster? Comparison of 11 versions from 1.1.5 to 3.0.0 alpha
Performance Test Results Distribution
Test results for different versions
- Performance 2005
- Is OpenOffice.org Getting Faster? benchmarks 5 common operations for OpenOffice.org versions 1.1.5 through 2.4.0 and DEV300_m3
- List of libraries loaded on OpenOffice.org 3.1 (DEV300m40) startup
This Wiki page should become the ultimate authority on performance issues. Meanwhile, here are links to performance informationat other places