Hi,
Bit of a general question about xsl:include.

We have a solution that transforms thousands of XML messages every hour.
Currently none of the stylesheets use the include functionality, each stylesheet just works on it's own.

I am looking at using shared stylesheets to cut down on code duplication, through the use of xsl:include. To be specific, every single transform action will use two xsl:include instances.

For a solution that does so many transforms, what sort of performance changes would I expect to see?
This is assuming that each XML message is the same size - roughly 10kb each for the inputs and outputs.

I appreciate that I haven't provided details of server capabilities, software, etc, but I'm just after a rough indication of the change in performance - is it a significant impact to use include?

Thanks in advance,

__________________
Neil Belch
Technical Officer
CDL

The views opinions and judgements expressed in this message are solely those of the author. The message contents have not been reviewed or approved by CDL.

The answer to performance questions always depends on which XSLT processor you are using.

However, I would expect that any costs incurred by xsl:include occur entirely at stylesheet compile time, and not at stylesheet execution time. It is of course vital if you are applying the same transformation thousands of times per hour that you only compile it once at "start of day".

__________________
Michael Kay
http://www.saxonica.com/
Author, XSLT 2.0 and XPath 2.0 Programmer\'s Reference

The processor is Saxon-B 8.9 to be precise, and it's compiled only when the solution itself is reloaded (so not at every call).
Sounds like there is little issue to using includes - thanks for the response.

__________________
Neil Belch
Technical Officer
CDL

The views opinions and judgements expressed in this message are solely those of the author. The message contents have not been reviewed or approved by CDL.