Difference between revisions of "Performance/To-Dos"

From Apache OpenOffice Wiki
Jump to: navigation, search
(Work List and Progress)
 
(4 intermediate revisions by 3 users not shown)
Line 1: Line 1:
{{Performance}}
+
{{Performance}}  
 
The new [http://performance.openoffice.org/ performance project] just started, and we have to sort out our next todo's.
 
The new [http://performance.openoffice.org/ performance project] just started, and we have to sort out our next todo's.
  
Line 21: Line 21:
 
* [[Writer_Performance|Writer]]
 
* [[Writer_Performance|Writer]]
 
* [[Impress_Performance|Impress]]
 
* [[Impress_Performance|Impress]]
* [[Base_performance|Base]] - lots to do
+
* [[Base/Performance|Base]]
  
 
==== system issues ====
 
==== system issues ====
Line 47: Line 47:
 
* -Bdirect linking
 
* -Bdirect linking
 
* FIXME - Malte - we should really have your list embedded here ...
 
* FIXME - Malte - we should really have your list embedded here ...
 
+
* [[An introduction of asynchronous loading in Symphony]]
 
+
  
 
[[Category:Performance]]
 
[[Category:Performance]]

Latest revision as of 03:19, 2 May 2012

Performance 170.png
Performance Project

performance.openoffice.org

Quick Navigation

Team

Communication

Activities

  • ToDo List
About this template


The new performance project just started, and we have to sort out our next todo's.

For now, you might use my old list from 2005, which might be a little bit outdated. Maybe you find some hints in the area of your expertise where you want to start working on:

OpenOffice.org Performance Activities as of 2005.

Moved here from the main performance wiki page:

Known areas for improvement

Configmgr[new]

Component issues

system issues

  • Linux / Linking - relocation processing is very slow ( ogg video, odp slides ) several 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.
    • exporting Vague linkage more cleverly & using RTLD_LOCAL where possible
    • basic linker optimizations:
      • don't export *UND* in .hash table
      • sort syms & dynsym entries more intelligently
      • .hashvals optimisation
  • Linux / I/O scheduling & pre-loading is poor

General I/O & memory issues

  • Image strip layout - our images strips are huge & unwieldy, layed out horizontally and are 'cached' in scattered files - this is fixed in CWS ka009, which never seems to get integrated.
  • Configuration information scattered across many files
  • UI configuration - tons of scattered files
  • .rdb files - loads of empty space, mmap + random access pattern

Work List and Progress

Personal tools