Parser performance is judged mostly on speed and memory consumption. How long does it take for the parser to parse a large document( > !MB ) and what is its memory footprint. While choosing a parser you will have to consider issues such as -
The average size of the XML document(s) on hand.
The complexity of the documents.
The available memory resources on the machine.
The acceptable latency.
Once the document is parserd, do you need random access to the nodes? Is sequential access too limiting for your application?
Conformance to evolving XML standards and support for new specs and technologies. For instance, whether the parser has Schema support, Support for various DOM Levels etc
Cheers! ------------------ Ajith Kallambella M. Sun Certified Programmer for the Java�2 Platform. IBM Certified Developer - XML and Related Technologies, V1.
Open Group Certified Distinguished IT Architect. Open Group Certified Master IT Architect. Sun Certified Architect (SCEA).
Joined: Feb 06, 2001
great words Ajith !! Can you even give some information on the performance for the parsers available in the market. A comparison chart would be highly appreciated.
Joined: Mar 17, 2000
Checkout this link - http://184.108.40.206/developerlife/parsertest2/performance.html It has some benchmarking statistics for various popular parsers. A word of caution though, this data is quite old and there are newer versions of these parsers available today. Not to mention there are more number of parsers available today that are not in the list. So take the data with a pinch of salt ------------------ Ajith Kallambella M. Sun Certified Programmer for the Java�2 Platform. IBM Certified Developer - XML and Related Technologies, V1.