From: Mark Swanson <mark_at_ScheduleWorld.com>
Date: Fri, 20 Jan 2006 14:46:10 -0500

> a lot of object; VTD-XML doesn't. So VTd-Xml
> should hold the edge both in memory and performance...
> The best way is to try it...

Tried it. VTD wins by a wide margin in memory and performance
(throughput as well as memory pressure placed on the GC by object
creation) over XmlBeans. I used the VTD Java API and the XmlBeans API to
loop through parse, get some element attribute value as String 20 times
in loops of 5000.

I'm now even more intrigued by an FI/VTD combo.

Cheers.

-- 
Free replacement for Exchange and Outlook (Contacts and Calendar)
http://www.ScheduleWorld.com/
WAP: http://www.ScheduleWorld.com/sw/WAPToday?id=4000&tz=EST
WebDAV: http://www.ScheduleWorld.com/sw/webDAVDir/4000.ics
VFREEBUSY: http://www.ScheduleWorld.com/sw/freebusy/4000.ifb