Bug #4341
closed
Performance degraded after moving from Saxon 8.9 to 9.8.0.15 (use case CXML)
0%
Description
Customer upgraded to the latest version of our product which uses Saxon 9.8.0.15 EE. They came from an older version which used Saxon 8.9.0.14. They process thousands of documents per day with hundreds of XSLs. For two use cases (see other Saxon issue reported for the second use case) they see dramatic performance decrease which impacts their business.
Below you will find test results from our product(Sonic), from Saxon commandline and also from a Java test utility that simulates how our product uses Saxon. The ZIP contains sonicTest_CXML.cmd and saxonTest_CXML.cmd which allow you to reproduce the tests that I did. Further it contains the source code of the SonicXSLCmdLine.
We have to stick to 9.8 for now as we still have Java 7 support. Therefore we would appreciate a patch release for 9.8 once the cause has been identified.
I sent you a download link for the ZIP with the reproducible to the support email address. The ZIP contains sensible customer data and therefore password protected. (please do not attach here!)
"CXML" use case summary:
With Saxon 8.9 as the baseline the processing time is 2x inside Sonic with Saxon 9.8.0.15. Saxon commandline processing time is 3x. SaxonXSLCmdLine is showing similar results to Sonic product.
Test results:
Inside Sonic product: 17min = 1020 sec with Saxon 8.9 41min = 2460 sec with Saxon 9.8 34min = 2040 sec with Saxon 9.9
CXML XSL results form Saxon commandline: Saxon 8.9.0.4: 763290 ms Saxon 9.1.0.9: 813310 ms Saxon 9.8.0.15: 2120170 ms Saxon 9.9.1.2: 2021810 ms
SaxonXSLCmdLine RESULTS: XSL: EDW_Adapters\XSLs\CXMLTOEDW.xsl JVM arguments: -Dxsl.useTracing=false -Dsaxon.optimizationLevel=-c Saxon 9.8.0.15: 2112930 ms Saxon 9.9.1.2: 2016450 ms
SaxonXSLCmdLine RESULTS: XSL: EDW_Adapters\XSLs\CXMLTOEDW.xsl JVM arguments: -Dxsl.useTracing=false Saxon 9.8.0.15: 2156000 ms Saxon 9.9.1.2: 1959450 ms
Please register to edit this issue
.