[jdom-interest] performance on tonights CVS

[David D. Lucas]

I pulled down the CVS source tonight and wanted to know how the current 
JDOM is handling the parsing as compared to JDOM beta 7.  I used 
different SAX parsers and the samples.TestXMLOutput (slightly modified) 
to run a few repeating tests.

What I have found seems to indicate that outputting a JDOM tree to XML 
for a large file (1.85MB) is about 3 times faster now than JDOM beta 7.
Great job!!!

However, something in the way SAX is being used has impacted my Builder. 
build performance which has slipped some 40% in the wrong direction.
I have not profiled it yet, but was wanting to know if anyone has a 
quick explaination or suggestion on how to get it back up to beta 7 
build speeds.

As a side note, it looks like memory usage is a bit better in the 
current CVS snapshot than beta 7.

Any help would be appreciated.  I know that 1.85MB XML is a bit large, 
but that is what my client wants.   We are processing some large 
MQSeries messages and are using JDOM to manipulate the information.

Thanks in advance,
Dave

-- 

+------------------------------------------------------------+
| David Lucas                        mailto:ddlucas at lse.com  |
| Lucas Software Engineering, Inc.   (740) 964-6248 Voice    |
| Unix,Java,C++,CORBA,XML,EJB        (614) 668-4020 Mobile   |
| Middleware,Frameworks              (888) 866-4728 Fax/Msg  |
+------------------------------------------------------------+
| GPS Location:  40.0150 deg Lat,  -82.6378 deg Long         |
| IMHC: "Jesus Christ is the way, the truth, and the life."  |
| IMHC: "I know where I am; I know where I'm going."    <><  |
+------------------------------------------------------------+

Notes: PGP Key Block=http://www.lse.com/~ddlucas/pgpblock.txt
IMHO="in my humble opinion" IMHC="in my humble conviction"
All trademarks above are those of their respective owners.