> Ideal should for the XSLTC engine to recognize the JVM it runs in (via > system properties) and tune the generated bytecode on the > running JVM. I > assume this could give some 20/30% more speed improvement, but it's a > potentially harmful thing to do since it might duplicate code and > requires *lots* of guesses on how the JVM works internally.
IMO beside CPU the garbage creation is also an issue (especially on SMP systems where the single threaded GC limits the CPU usage, at least pre 1.4 VMs). Maybe I will find the time to start OptimizeIt and do some tests in the next days.
