Difference between revisions of "Performance"
From Apache OpenOffice Wiki
(→system issues) |
|||
Line 1: | Line 1: | ||
+ | As George Ou has famously said, "It doesn't matter how fast the CPU is, OpenOffice is just bloated." | ||
+ | |||
== Known areas for improvement == | == Known areas for improvement == | ||
Line 8: | Line 10: | ||
=== General I/O & memory issues === | === General I/O & memory issues === | ||
− | * Config mgr - scattered files | + | * [[DbConfig|Config mgr]] - scattered files |
* UI configuration - tons of scattered files | * UI configuration - tons of scattered files | ||
* .rdb files - loads of empty space, mmap + random access pattern | * .rdb files - loads of empty space, mmap + random access pattern |
Revision as of 23:07, 4 February 2006
As George Ou has famously said, "It doesn't matter how fast the CPU is, OpenOffice is just bloated."
Contents
Known areas for improvement
system issues
- Linux / Linking - relocation processing is very slow ( ogg video, odp slides ) two possible ways to fix that
- re-ordering symbol & elf hash tables to improve cache locality, lots of good & simple ideas here.
- -Bdirect implementation [1] - gaining little traction.
- Linux / I/O scheduling & pre-loading is poor
General I/O & memory issues
- Config mgr - scattered files
- UI configuration - tons of scattered files
- .rdb files - loads of empty space, mmap + random access pattern
Helpful tooling
- Linux/cold-start simulator
- relocstat - dump relocation data
- RTL_LOGFILE - export RTL_LOGFILE=/tmp/foo
- valgrind - debug / trace memory usage
- speedprof - a quick / hackish sampling full-stack-trace profiler & visualisation tool
- APPR - a performance regression tool suite
Approaches being worked on
- Config refactor - reduce seeks/files, better caching
- Disk Access
- -Bdirect linking
- FIXME - Malte - we should really have your list embedded here ...
Other Pages
This Wiki page should become the ultimate authority on performance issues. Meanwhile, here are links to performance informationat other places