15
2005
Processing 2Gb XML Files with StAX
As part of a recent CJUG XML Smackdown we played with processing a very large (2Gb) XML file using SAX & StAX. I was doing the StAX bit (using Woodstox), and I learnt some very interesting lessons on processing large XML files along the way.
The file we used to demo was a large rdf file from the dmoz directory. Its compressed (gzip) size is 299Mb, but it unzips to just under 2Gb. The test was to iterate all elements and pull the urls out of the “about” attribute.
I tried the demo on three machines. A Mac Mini (290secs), An old Thinkpad (370secs), and a newish AMD 2.4 Linux box (80secs). The results were very interesting – I/O was definitely the killer on the slower boxes. To experiment further, I changed the code to read from the original 300Mb file using a GZipInputStream – and the Thinkpad came in at 270secs – I wiped off nearly a third of the time! No such luck on the AMD box (which has a SATA hard disk) – where throughput actually slowed when using the Gzip method.
Interestingly the Sax performance was nearly identical in all tests (mostly slightly faster than Stax, but sometimes slightly slower – but either way not really significant given the amount of processing).
So the learning experience for me:
- StAX is definitely a goer (and performant) for very large files
- Don’t ever think that I/O is an insignificant cost in any large operation!
It’s sure no empirical test – really just a back-of-a-napkin kinda thing. But it was fun to demo, and gave me my first ever chance to use a GZipInputStream!
5 Comments + Add Comment
Leave a comment
Glen Smith
Archives
- April 2012
- March 2012
- January 2012
- November 2011
- October 2011
- September 2011
- August 2011
- July 2011
- June 2011
- April 2011
- March 2011
- January 2011
- November 2010
- October 2010
- September 2010
- August 2010
- July 2010
- June 2010
- May 2010
- April 2010
- February 2010
- January 2010
- December 2009
- November 2009
- October 2009
- September 2009
- August 2009
- July 2009
- June 2009
- May 2009
- April 2009
- March 2009
- December 2008
- November 2008
- October 2008
- September 2008
- August 2008
- July 2008
- June 2008
- May 2008
- April 2008
- March 2008
- February 2008
- January 2008
- December 2007
- November 2007
- October 2007
- September 2007
- August 2007
- July 2007
- June 2007
- May 2007
- April 2007
- March 2007
- February 2007
- January 2007
- December 2006
- November 2006
- October 2006
- September 2006
- August 2006
- July 2006
- June 2006
- May 2006
- April 2006
- March 2006
- February 2006
- January 2006
- December 2005
- November 2005
- October 2005
- September 2005
- August 2005
- July 2005
- June 2005
- May 2005
- April 2005
- March 2005
- February 2005
- January 2005
- December 2004
- November 2004
- October 2004
- September 2004
- August 2004
- July 2004
- June 2004
- May 2004
- March 2004
- February 2004
- January 2004
- December 2003
- November 2003
- October 2003
- September 2003

An article by Glen





hey glen do you have a sample code on how youve run the stax parser?
Sure. You can download the slides from the CJUG presentation and checkout the code in the “stax” package. If you’re using Woodstox, you’ll probably need to drop in the Woodstox jars (not sure which Stax parser I used for the demo) – got a feeling it was the Sun one. Enjoy.
Just checked it, and I did use Woodstox for the demo…. Which makes sense given the blog entry above…
Hi Dear,
Would you please tell me whether or not it is possible in C#.net or any of the .net application.
Plz, i am in big trouble
you might also want to try vtd-xml, wich supports xpath over xml doc up to 256 gig
http://vtd-xml.sf.net