XSLT transformation as batch operation - performance
Posted: Fri Jun 23, 2017 10:59 pm
Hi all,
I have read the topics in the thread "XSLT in batch" and I was glad to learn something about XML Refactoring.
We are building some DTD migration XSLT which ultimately must be applied to thousands of XML documents distributed into a folder structure. So, right-clicking the folder and the Transform > Transform with command is an easy solution – at least for testing the XSLT on a certain number of files. (BTW, we can not use {$cf} as a target, because we need all files intact for access during the processing of later files.)
I am somewhat not satisfied with the performance of this batch transformation. As I am under the impression that Oxygen parses the XSLT new for every file found. Is that correct?
Are there ways to cache the parsed XSLT?
Or, are there ways using Saxon EE to create and execute an SEF file?
Or, do you have other suggestion for increasing batch performance? (Apart from making sure the XSLT is well-written.)
Before I have one of our developers write a simple transformation runner Java application, I am wondering if I already get the maximum performance from Oxygen or if there are options to enhance this. We would not blame OxygenXML if this use case is not supported, I just don't want to miss a feature. There is so much to learn…
Thanks a lot for your time,
- Michael
I have read the topics in the thread "XSLT in batch" and I was glad to learn something about XML Refactoring.
We are building some DTD migration XSLT which ultimately must be applied to thousands of XML documents distributed into a folder structure. So, right-clicking the folder and the Transform > Transform with command is an easy solution – at least for testing the XSLT on a certain number of files. (BTW, we can not use {$cf} as a target, because we need all files intact for access during the processing of later files.)
I am somewhat not satisfied with the performance of this batch transformation. As I am under the impression that Oxygen parses the XSLT new for every file found. Is that correct?
Are there ways to cache the parsed XSLT?
Or, are there ways using Saxon EE to create and execute an SEF file?
Or, do you have other suggestion for increasing batch performance? (Apart from making sure the XSLT is well-written.)
Before I have one of our developers write a simple transformation runner Java application, I am wondering if I already get the maximum performance from Oxygen or if there are options to enhance this. We would not blame OxygenXML if this use case is not supported, I just don't want to miss a feature. There is so much to learn…
Thanks a lot for your time,
- Michael