I have completed some benchmarking of various combinations of the
Xalan/Xerces or Crimson packages and have attached my results.
Notes:
- DNF = did not finish (I couldn't wait around that long)
- The memory footprint is very rough as it was obtained using
Runtime.freeMemory()
- I only tes
Title: RE: XPathAPI performance problems
In the several projects that I have worked on that are
XML based, only a small amount of the XPath queries
are used for XSLT processing (unfortuneately).
Most of my XPath is querying "background" documents for
their data, most of which
you "Walsh, Eric" <[EMAIL PROTECTED]> wrote
> For the record I say you just throw the old routines back
> in and call it even, especially since very little of my
> XPath queries are XSLT originated.
I know there are definite issues with our XPathAPI performance, but I
think this is actua
Title: RE: XPathAPI performance problems
For the record I say you just throw the old routines back
in and call it even, especially since very little of my
XPath queries are XSLT originated.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, January
H. We knew we might be deoptimizing DOM performance in exchange for
better SAX performance, and in order to optimize for the needs of the XSLT
processor... but I agree we should pause and think carefully about this.
One possible approach: Pre-analyse the XPath to see if it's going to need
to
Just as Eric (Walsh) stated, not only is the perfomance drastically
degredated, I found that it becomes increasing bad as I query farther down
the document, and performance degredates at a fairly steep rate.
I found that the Xalan 2.1 release is almost as fast as the previous release
we were using
Title: RE: XPathAPI performance problems
Thanks for the info. Reading the explaination of DTM on
apache.org, it seems funny that this was done to speed up
XPath Querying, it seems querying an object model you already
have would be much more effecient than building a new one.
Your
> takes about 20ms. It seems like the XPath routine is starting
> from the top of document, no matter if you give it a parent or
> not.
That may in fact be true in the current code.
Your XPath may want to search upward/backward from the starting node
(ancestor or previous axes). That means thos
Title: RE: XPathAPI performance problems
I am also having XPath performance problems (which I
submitted to the dev group). The problem seems to have
nothing to with querying a document multiple times.
In my case, I am parsing an XML schema file by first getting
the complexType nodes then
If you're going to query a single document multiple times, see the class
CachedXPathAPI. If I remember correctly, its javadoc summarizes the issues
involved.
D]To: [EMAIL PROTECTED]
tmail.com> cc:
Subject: XPathAPI performance
problems
I am having some serious performance issues with XPathAPI processing using
the latest releases of Xalan and Xerces (Xalan j 2.2.0 and Xerces 2 D14).
I have tried a very simple test case which attempts using a DOM document
which consists of about 1000 sibling elements directly beneath the documen
12 matches
Mail list logo
