Hi there, has anybody else noticed that the performance of Xalans-C++ Xpath
evaluation is degrading catastrophically with large documents, if the
preceding:: axis is used ?
I have built an application that uses only the Xpath component of Xalan ( no
XSLT ), to find nodes in an XML Document.
The Sample-Document has about 174000 Element nodes, maximum depth of nesting
is about 20.
Searching for the 99999.th node in forward direction is quite fast:
(//*)[99999]
takes about 1.2 seconds (on a 700 MHz PentiumIII under WinNT) for the pure
Xpath Evaluation, ( plus 4 seconds for parsing the Document )
In contrast,the question for the same node, formulated as:
(//*)[100000]/preceding::*[1]
takes about 75 seconds, what is 2 ordes of magnitude slower.
BTW, Saxon needs about 5 Seconds for the complete Parsing and evaluation for
both queries.
