The Java XQuery code is typically 25%-50% faster than running interpreted, but it can be anything from 0% to 80% depending on the query. The biggest benefits seem to come when doing a lot of arithmetic.
 
Michael Kay
http://www.saxonica.com/


From: saxon-help-bounces@lists.sourceforge.net [mailto:saxon-help-bounces@lists.sourceforge.net] On Behalf Of martin.me.roberts@bt.com
Sent: 22 July 2008 16:25
To: saxon-help@lists.sourceforge.net
Subject: Re: [saxon] Compiling a Stylesheet

Michael,
  Does the java XQuery run much quicker?
 
Martin


From: saxon-help-bounces@lists.sourceforge.net [mailto:saxon-help-bounces@lists.sourceforge.net] On Behalf Of Michael Kay
Sent: 22 July 2008 16:20
To: 'Mailing list for the SAXON XSLT and XQuery processor'
Subject: Re: [saxon] Compiling a Stylesheet

Saxon-SA now has the ability to generate Java source code from XQuery - this is then executed directly by the JVM (though of course it needs Saxon as a runtime library.
 
But the (older) facility for "compiling" stylesheets is rather different. It basically takes the optimized syntax tree produced by the Saxon compile-time code and serializes it as a data structure on disk, so that it can be reloaded and executed at any time. Frankly, there are no significant performance advantages in doing this compared with recompiling the source.
 
Michael Kay
http://www.saxonica.com/


From: saxon-help-bounces@lists.sourceforge.net [mailto:saxon-help-bounces@lists.sourceforge.net] On Behalf Of martin.me.roberts@bt.com
Sent: 22 July 2008 15:22
To: saxon-help@lists.sourceforge.net
Subject: [saxon] Compiling a Stylesheet

Michael,
  what actually happens when you compile a stylesheet?
 
  does it become an executable piece of code i.e. java Class(es)?
 
Martin