|About this template|
- 1 The performance project
- 2 Deliverables
- 3 Work in progress
- 4 Performance Status
- 5 Tooling and TC
- 6 Integrated improvements
- 7 Other Resource
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.
- A test system for collecting reproducible and comparable performance data of OpenOffice.org master builds.
- A test methodology for measuring and comparing performance data of OpenOffice.org master and CWS builds.
- Lightweight tools that automatically collect performance data and assist developers in identifying performance bottlenecks.
- Real life test scenarios which will also be reflected in the automatic performance tests.
- OpenOffice.org startup performance improvements
- OpenOffice.org ODF load/save performance improvements
- Performance oriented analysis of OpenOffice.org's framework
Work in progress
Probably a lot - please continue here.
- Performance - Analysis (Windows)
- What's going on in Writer load/save performance see here
- Calc/Performance/The Ou case
- Calc/Performance/Updating Row Heights
- Calc/Performance/querying data within functions
- Calc/Performance/Incremental Saving
For finished work see Calc/Done/Performance.
- Impress OpenDocument load/save performance Impress/Performance#OpenDocument
- Impress slideshow performance Impress/Performance#Slideshow
Load/Save General (Non Application Specific Tasks)
User Experience Index (UEI)
Distribution and Tracing
Analysis of Performance
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
- Startup of DEV300 builds on linux
Tooling and TC
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
- VTune - profiler for Windows and Linux, commercial product
- TrueTime - profiler for Windows, commercial product
- AMD CodeAnalyst - profiler for windows, optimized for AMD, VisualStudio integration
- Performance/Tools/VerySleepy (HowTo) Very Sleepy 0.4 - open source profiler for windows, works on any cpu, very easy to use
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
- Multiplatform OpenOffice.org 3.0 Benchmark including vanilla OOo, StarOffice, Go-oo, Portable OOo on Windows XP and Ubuntu 8.10
This Wiki page should become the ultimate authority on performance issues. Meanwhile, here are links to performance informationat other places