xslt function 7 times slower in 2025a compared to 2023a ?

Hi,

I'm noticing a significant performance loss in the xslt() funtion going from 2023a to 2025a.

A transform that only takes 3.6 seconds in 2023a takes 24.4 seconds in 2025a. I did read there are changes to the function, i.e. one can select the XSLT processing engine but all options are just as slow.

Is there a way to regain the performance from 2023a in 2025a for the xslt transform?

[John D'Errico]

Please give an example of use where you see the slowdown. That will help greatly. Anyway, you will probably want to contact tech support in the end, and they will certainly need to see exactly that.

[Koen]

Hi John, thanks for the feedback. Unfortunately I can't share the xml and xsl file on here but I use the same command in both releases:

tic;result = xslt(xmlFile, xslFile, "-tostring");toc

Meanwhile, I saved the xslt function from 2023a (and one other dependent function) and used it in 2025a. That runs in 2025a with the same speed as in 2023a.

[Koen]

Looking a bit more in the code, the legacy mode should be equivalent to the 2023a function and triggers by using "jaxp" as the processing engine but I used "JAXP" and it turns out to be case sensitive ...