Each document has been processed 10 times for each of the 10 runs.
The measured time was the sum of the user and system times, as returned by the Analysis This test shows that Xalan and Saxon are performing equally and that compiling style sheets to Java bytecode may improve performances up to 40% when compared to the classic implementations, such as Xalan or Saxon on Crimson.
The problem was kept simple to accommodate the different capabilities of those technologies and therefore it may not have revealed the richness and power of the more sophisticated ones like XSLT and XPath.
In this respect, the performance tests presented here may be considered as micro-benchmarks.
It's using both Crimson and Xerces' SAX and DOM implementations.
The intent here is to measure the impact of validation on the processing time.
This benchmark compares the performances of SAX and DOM with and without validation.
In the context of this document, we are only considering parsers which even when non-validating, load and parse the DTD and the entities referenced in the document.
This allows, for example, the entities to be substituted, the attribute values to be normalized and their default value properly substituted, so that the application can run unchanged when switching from validation to non-validation of the input document.
As of today, no less than six extensions to the Java Platform empower the Java developer when building XML-based applications: This article is the second in a series of three.
The first one gave an overview of the Java API for XML Processing (JAXP), and the technologies that it directly or indirectly provides to the Java developer or technologies that rely on it in order to process XML documents.