Re: XSLTPROC performance

Play the video

Subject: Re: XSLTPROC performance
From: Abel Braaksma <abel.online@xxxxxxxxx>
Date: Fri, 21 Dec 2007 14:15:03 +0100

Colin Paul Adams wrote:

    Abel> Often, people measure the timing including the startup of
    Abel> the JVM. If you use Saxon properly, you keep the classes and
    Abel> the compiled stylesheets in memory. You'll see that this
    Abel> will improve your performance a lot, especially when talking
    Abel> about many small XML files.

No it won't, not unless you run it a second time!

So it depends.

Well, what I meant is removing the startup time of the JVM. Suppose you run 1000 XML files from the commandline (one "java -jar saxon.jar ..." per file), or you run the same 1000 XML files by calling+processing them with the document() function, you will see a large decrease in total running time.

Compiling the stylesheet and keeping the compiled stylesheet in a pool adds another performance gain when you need that stylesheet more than once.

Of course, these general performance improvements are applicable to just about any processor on any system. But the JVM is notorious for adding lots of extra overhead.

Cheers,
-- Abel Braaksma

Current Thread

Re: XSLTPROC performance, (continued)

<- Previous	Index	Next ->
Re: XSLTPROC performance, Colin Paul Adams	Thread	Re: XSLTPROC performance, Andrew Welch
Re: Santa has come early, Florent Georges	Date	Re: XSLTPROC performance, Andrew Welch
	Month

PURCHASE STYLUS STUDIO ONLINE TODAY!

Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!

Download The World's Best XML IDE!

Accelerate XML development with our award-winning XML IDE - Download a free trial today!

Subscribe in XML format

RSS 2.0
Atom 0.3

XML Editor - Download a 15 Day Free Trial Now >

See What's New in Stylus Studio >

Buy Stylus Studio - XML Editor - Now >