[jdom-interest] XSLT-Performance with Xalan/TrAX/JDOM

[Dennis Sosnoski]

JDOM documents are actually a little larger than DOM documents, at least for
documents in the 100-200K range (though I'd suspect this is true in all cases). I've
published a comparison test that shows this at
http://www.sosnoski.com/opensrc/xmlbench/index.html The use of the Java Collections
API that makes JDOM (as well as ElectricXML and dom4j) easy to use also make for
larger memory representations, so it's likely to stay this way.

I'll update the tests and test results the weekend after next, and if the JDOM Beta 7
is out by then I'll switch to using that in the tests.

Going to ArrayList for the backing collections, as we've previously discussed on this
list, would certainly help both size and performance in general. I think this is one
of the reasons dom4j comes out ahead on the current performance tests shown on the
site.

  - Dennis

Stephan Weiss wrote:

> I tried out org.jdom.transformation.JDOMSource / ...JDOMResult, cause
> Xalan just did the job slowly, when i was using org.w3c.dom.Document. I
> thought, that because JDOM-trees are much smaller (in memory) than DOMs,
> transformation with JDOM could be faster. But as I have seen in my tests
> it is much more slowly. Can anyone explain this to me ?
>
> --
>
> Stephan Weiss <s.weiss at globalview.de>
> Entwicklung - Global View GbR
>
> T +49 30 443 890 - 0
> F +49 30 443 890 - 10
>
> http://www.globalview.de
>
> _______________________________________________
> To control your jdom-interest membership:
> http://lists.denveronline.net/mailman/options/jdom-interest/youraddr@yourhost.com