View Single Post
  #4 (permalink)  
Old June 12th, 2008, 09:55 AM
mhkay's Avatar
mhkay mhkay is offline
Wrox Author
Points: 18,487, Level: 59
Points: 18,487, Level: 59 Points: 18,487, Level: 59 Points: 18,487, Level: 59
Activity: 0%
Activity: 0% Activity: 0% Activity: 0%
Join Date: Apr 2004
Location: Reading, Berks, United Kingdom.
Posts: 4,962
Thanks: 0
Thanked 292 Times in 287 Posts

>The speed of a Java XSL compiler versus an interpreter isn't even a contest.

What makes you think that? It simply isn't true.

I think you'll find that the benefits of compiling are less dramatic than you think. That's partly because most of the time is likely to be spent in the run-time library, which will be identical in both cases. Saxon-SA will output Java code which can be compiled, and the performance benefit is typically about 25% (though within a range from 0% to +50%). That's useful to have, but far smaller than the variations between different XSLT processors.

Having said that, it might be worth looking at the Intel XSLT processor. I don't know if it meets your definition of a compiler - to be honest, the boundaries between compilers and interpreters are getting very fuzzy these days - but it might meet your needs. Unfortunately it's only XSLT 1.0 at the moment.

Michael Kay
Author, XSLT Programmer's Reference and XPath 2.0 Programmer's Reference
Reply With Quote