Skip to Content.
Sympa Menu

xom-interest - Re: [XOM-interest] New FAQ entry on otpimizing XOM

xom-interest AT lists.ibiblio.org

Subject: XOM API for Processing XML with Java

List archive

Chronological Thread  
  • From: Wolfgang Hoschek <whoschek AT lbl.gov>
  • To: Elliotte Harold <elharo AT metalab.unc.edu>
  • Cc: xom-interest <xom-interest AT lists.ibiblio.org>
  • Subject: Re: [XOM-interest] New FAQ entry on otpimizing XOM
  • Date: Mon, 17 Jan 2005 08:43:48 -0800

On Jan 17, 2005, at 2:08 AM, Elliotte Harold wrote:

I've added a FAQ entry on speeding up XOM programs. See:

http://www.xom.nu/faq.xhtml#d0e213

If anyone has any other techniques they'd like to suggest, please post them here. Thanks!

• Don't use XPath. XPath is currently implemented for convenience, simplicity, and robustness; not performance. It has not yet been profiled or optimized. (This may change in the future.) If you do use XPath, you might want to consider using NUX or SAXON, both of which provide some options to speed up XPath, instead of XOM 1.1's built-in XPath support.

XPath implementations do not need to crawl like turtles :-)

For simple queries, Nux and Saxon run at up to 2000 (100000) executions/sec over 100 KB (0.5) KB input documents = 200 (50) MB/s on a commodity PC. In fact, the XPath impl. hardly shows up at all in the profiler when running XPath/XQuery in a streaming NodeFactory individually against each of millions of XML records, which is considered a rather stressful testcase...

Wolfgang.

-----------------------------------------------------------------------
Wolfgang Hoschek | email: whoschek AT lbl.gov
Distributed Systems Department | phone: (415)-533-7610
Berkeley Laboratory | http://dsd.lbl.gov/~hoschek/
-----------------------------------------------------------------------





Archive powered by MHonArc 2.6.24.

Top of Page