Difference between revisions of "Performance"
From Apache OpenOffice Wiki
m (→Known areas for impovement) |
m (→Helpful tooling) |
||
Line 19: | Line 19: | ||
* [[valgrind]] - debug / trace memory usage | * [[valgrind]] - debug / trace memory usage | ||
* [[speedprof]] - a quick / hackish sampling full-stack-trace profiler & visualisation tool | * [[speedprof]] - a quick / hackish sampling full-stack-trace profiler & visualisation tool | ||
+ | * [[APPR]] - a performance regression tool suite | ||
== Approaches being worked on == | == Approaches being worked on == |
Revision as of 21:52, 15 December 2005
Contents
Known areas for improvement
system issues
- Linux / Linking - relocation processing is very slow 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