Difference between revisions of "Calc/Performance/misc"
(→ScBaseCell) |
m (Calc Performance Calc moved to Calc Performance) |
(No difference)
|
Revision as of 09:43, 20 March 2006
Contents
Calc Optimisation Opportunities
There are a lot of opportunities in calc for various reasons. This list needs extending:
Cell size
Basic problem: the most basic cell consumes about 50bytes all told, more complex cells consume far more memory, there are a number of simple & obvious things to re-factor here.
It's trivial to calculate the average cost - simply create a sheet with several thousand cells in it, and measure the heap allocation change on load - with memprof or some other tool, then divide by the number of cells. Similarly, wins are easy to measure this way.
ScBaseCell
sc/inc/cell.hxx; code in sc/source/core/data/cell.cxx & cell2.cxx
class ScBaseCell { protected: ScPostIt* pNote; SvtBroadcaster* pBroadcaster; USHORT nTextWidth; BYTE eCellType; // enum CellType - BYTE spart Speicher BYTE nScriptType;
Every cell carries this overhead; note that a chunk of it is not necessary for many cells:
- ScPostIt pointer - very, very infrequently used - we have almost no post-it note per cell.
- SvtBroadcaster - used by cells that are referenced (by a single cell (ie. non-range) reference) from another cell - again, a sub-set of all cells.
Solutions: a little re-factoring required, but stealing a bit-field from eCellType to denote a 'special' cell:
class ScBaseCell { protected: USHORT nTextWidth; BYTE eCellType : 7; // enum CellType - BYTE spart Speicher bool bSpecial : 1; // other information to be looked up elsewhere BYTE nScriptType;
The 'bSpecial' flag could be used to denote that there is a 'note' for this cell (in a separate hash), or that this cell has a single-cell dependant. So - we can save 2/3rds of the base size with fairly little effort.
ScStringCell
In Excel similar strings across the sheet are shared. Our string class includes a sharable, immutable reference counted string - but it's not clear that we use this as intelligently as we should - pwrt. XML import / export. Possibly we should be trying to detect common strings there with a small back-hash.
ScFormulaCell
There are a number of problems here:
- redundant data: apparently we store redundant data for values. Certainly we store the 'rendered' or computed value of the cell regardless of whether it is likely to be rendered.
- ScFormulaCell inherits from svt/inc/listener.h - which has a virtual destructor, hence we have a vtable pointer per instance too (most likely unnecessary), as well as the listener list.
- Document pointer - as in the ScEditCell structure we lug around a document pointer we should 'know' as implicit context.
In-sheet objects
Horribly slow - some VCL & svx issues here.
Large / complex pivot sheets
Jody has some sample data here - links ? - internal Novell sheet (commonly used) taking ~3 hours to re-compute.
threaded calculation
Ideally to scale to hyper-threaded machines we need to crunch a workbook's dependency graph & then thread the calcuation.