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
--~------------------------------------------------------------------
XSL-List info and archive: http://www.mulberrytech.com/xsl/xsl-list
To unsubscribe, go to: http://lists.mulberrytech.com/xsl-list/
or e-mail: <mailto:xsl-list-unsubscribe(_at_)lists(_dot_)mulberrytech(_dot_)com>
--~--