Subject:Built in XSLT Processor Too Slow Author:Michael Lange Date:30 Aug 2006 01:48 PM
When I execute a scenario using the build in processor it is so slow that it never finishes (and I have waited over a 1/2 hour). If I switch to the MS 4 external processor (does not support debugging) it finishes the same scenario in less in about 15 seconds.
The same slowness occurs with external processor such as Saxon that do support debugging. I am guessing there is a lot of overhead related to the debug support. I am just trying to run it and not debug it. Is there a way to turn off debug overhead?
Subject:Built in XSLT Processor Too Slow Author:Ivan Pedruzzi Date:30 Aug 2006 05:13 PM
Michael,
The overhead is not just for debugger and profiler but for the back-mapping as well.
To run Saxon without overhead use XSLT -> Generate Java code.
Stylus Studio will create a simple standalone application that
you can use to invoke your transformation.