Choosing a Tree Model
Saxon provides several implementations of the internal tree data structure (or tree model).
The tree model can be chosen by an option on the command line (
-tree:tiny for the
-tree:linked for the linked tree). There is also a variant of the tiny
tree called a "condensed tiny tree" which saves space (at the expense of build time) by
recognizing text nodes and attribute nodes whose values appear more than once in the input
document. The tree model can also be selected from the Java API. The default is to use the
tiny tree model. The choice should make no difference to the results of a transformation
(except the order of attributes and namespace declarations) but only affects performance.
The "linked tree" is the only model to support in-situ updates, so if you are using XQuery Update you must choose this model.
Generally speaking, the tiny tree model is both faster to build and faster to navigate. It also uses less space.
The tiny tree model gives most benefit when you are processing a large document. It uses a lot less memory, so it can prevent thrashing when the size of document is such that the linked tree doesn't fit in real memory. Use the "condensed" variant if you need to save memory, and if your source data contains many text or attribute nodes with repeated values.
Saxon also offers the option
-tree:condensed. This delivers a TinyTree with
additional compression. Specifically, when a document contains multiple text nodes or
attribute nodes with the same string value, the condensed tree will "common up" the storage
for these nodes. This option gives a further reduction in memory usage, at the cost of slower
The linked tree is used internally to represent stylesheet and schema modules because of the programming convenience it offers: it allows element nodes on the tree to be represented by custom classes for each kind of element. The linked tree is also needed when you want to use XQuery Update, because unlike the tiny tree, it is mutable.
If in doubt, stick with the default.