Investigate Footprint Shrinkage of OpenOffice.org

Short Description
OpenOffice.org is mythically resource intensive, and as the largest free C++. application out there stress tests everything it touches: compiler, toolchain, …

Website: www.gnome.org | Filesize: 625kb

Content
Investigate Footprint Shrinkage of
OpenOffice.org
Michael Meeks ,
Tor Lillqvist
Sponsored by AMD www.novell.comO v e r v i e w
OpenOffice.org is mythically resource intensive, and as the largest free C++
application out there stress tests everything it touches: compiler, toolchain, I/O & swap
algorithms, memory allocators and so on.
This document analyzes the footprint of the writer component (since this is typical),
running under a GNOME desktop, though the results should be similar to those of other
environments. All analysis was performed (unless otherwise specified) with an OO.o
2.0.4 build on a SLED10 system.
Memo r y b r e a k d o w n
Overall pmap analysis
pmap is a standard tool for displaying information about process memory mappings.
It can be used for simple, but reliable measure of the memory problems:
Size / Mb RSS / Mb Dirty / Mb
Total 266 (104 unshared) 75 25
So - we require 75Mb of physical memory to do no more than start up writer, and
enter a few characters. Of this, only 19Mb (25%) is heap space. Thus to reduce memory
consumption it will be necessary to reduce both heap and code sizes.
Code breakdown analysis
We have ~43Mb of core OO….