Support #4626
closed
Caching of XSLT with s9api
0%
Description
Hi Saxonica team,
We are facing poor performances during our performance tests, which are caused by the disk storage of the XSLT files. So we are considering setting up a caching façade. From my understanding of the Saxon documentation, one XsltExecutable instance holds a complete compiled XSLT, including imports and includes. So when an imported (common/utility) XSLT is changed, the whole cache should be flushed.
Is this correct?
Best Regards, Emilien
Updated by Michael Kay almost 4 years ago
Yes, that's correct. (Technically, you don't need to flush the whole cache, only the XsltExecutables affected by the change to an included/imported module).
If you want to be smarter, consider using XSLT 3.0 packages in place of include/import, and then you can do independent compilation into XsltPackage objects.
Please register to edit this issue
.