Advantages of compiling a stylesheet with saxon

[Bruno Mascret]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello,

What are the advantages of compiling a stylesheet with saxon?
I'm searching several ways to fast the xsl transformation process; is a
compiled stylesheet faster than a non-compiled one?
Best regards,
Bruno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkrxhhIACgkQaOubDsBUvbvyrgCeIpieIkI0jNU8vMf6NTAj43QU
IUwAoJWwXMtXtG6aEhwgLPu+yFddhm2L
=lw5K
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help 

[Michael Kay]

>
> What are the advantages of compiling a stylesheet with saxon?
> I'm searching several ways to fast the xsl transformation
> process; is a compiled stylesheet faster than a non-compiled one?

If you mean creating the JAXP Templates object (or the s9api XsltExecutable)
once, and then using it repeatedly for multiple transformations, then the
savings are very considerable: building the templates object for a seriously
complex stylesheet can often take 500ms, when running it to transform a
small input document takes 2ms.

But saving the compiled stylesheet to disk (as done by the CompileStylesheet
command) has relatively little benefit, compared with re-creating it when
needed from the original source code. I haven't measured it recently, but
last time I did, it looked as if it really wasn't worth the trouble.
However, this is obviously something that may depend on your own situation
and I would encourage you to do your own measurements.

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay 


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help 

[Bruno Mascret]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Thanks for the answer!
Michael Kay wrote:
> If you mean creating the JAXP Templates object (or the s9api
XsltExecutable)
> once, and then using it repeatedly for multiple transformations, then the
> savings are very considerable: building the templates object for a
seriously
> complex stylesheet can often take 500ms, when running it to transform a
> small input document takes 2ms.
I experienced it. Initial build take 3000 ms (we have really complex
sheets) and then is quite immediate.
>
> But saving the compiled stylesheet to disk (as done by the
CompileStylesheet
> command) has relatively little benefit, compared with re-creating it when
> needed from the original source code. I haven't measured it recently, but
> last time I did, it looked as if it really wasn't worth the trouble.
> However, this is obviously something that may depend on your own situation
> and I would encourage you to do your own measurements.
That was what I meant... I have to find other optimization possibilities...
Best regards,
Bruno
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAkry3CoACgkQaOubDsBUvbuKxwCdFaYk+XcFS9s86FiINaRmixD/
a/8An1WuzTeAOPoDs2384GI5lVa7EY9i
=2yy7
-----END PGP SIGNATURE-----

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help 

[Michael Kay]

> I experienced it. Initial build take 3000 ms (we have really complex
> sheets) and then is quite immediate.

If it's taking that long after allowing for Java VM warm-up time, then it
might be worth investigating (though you haven't told me anything about the
size).

Experiment (in Saxon 9.2) with -opt:0 which switches off optimization. I
would be interested to know if this makes any difference.

Regards,

Michael Kay
http://www.saxonica.com/
http://twitter.com/michaelhkay 


------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
saxon-help mailing list archived at http://saxon.markmail.org/
saxon-help@...
https://lists.sourceforge.net/lists/listinfo/saxon-help