Re: approximation of memory footprint used by Xalan

> Sorry.  I didn't mean object as in Java object.  My initial thought
> was that 5 SubAllocatedIntVector objects were used per node and inside
> each SubAllocatedIntVector there is a int[][].   If the 5 objects
> always grow in synchronization and have the same column-width, would
> it be possible to use a  single (new) variant of SubAllocatedIntVector

Unfortunately I don't think there's any good opportunity there. While 
locality of reference might be improved, addressing overhead would also be 
increased.

> After looking through the Xalan code again, I don't think those 5
> objects mentioned earlier grow at the same rate and so my suggestions
> would not work .

There's a core set which are maintained in parallel (the basic document 
tree structure), then others which are used as needed to support the data 
content of the document; the latter are pointed to from the core set 
rather than being based from the same node index.