It's not surprising that it is slow. // is an expensive operation it
means search every node in the document, and you are doing it in a
nested fashion, so unless your system rewrites your stylesheet if your
time at least the square (or cube ?) of the number of nodes in your
document which can get slow...
Without knowing your input or problem it's hard to give specific advice,
except the advice that // should normally be avoided, either by using
explict paths or by the use of keys.
for the outer //ColGrp, if you know where they are then using
/a/b/c/ColGrp
is likely to be quicke, as it saves searching the entire document for
them.
for the inner loop you are searching the document for Col elements then
each time searching the document again for measures elements (this
search returns the same nodes each time, so it may be worth saving this
in variable before the Col loop, although your xslt system may be able
to do that rewrite automatically,
do you really need to apply templates to every Measures eleemnt in the
document, for every Col in the document? this seems unlikely but as I
don't know what the transform is I can't suggest any changes.
David
________________________________________________________________________
The Numerical Algorithms Group Ltd is a company registered in England
and Wales with company number 1249803. The registered office is:
Wilkinson House, Jordan Hill Road, Oxford OX2 8DR, United Kingdom.
This e-mail has been scanned for all viruses by Star. The service is
powered by MessageLabs.
________________________________________________________________________
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--