JAXB, SAX, DOM Performance

This post investigates the performance of unmarshalling an XML document to Java objects using a number of different approaches. The XML document is very simple. It contains a collection of Person entities. 

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>

There is a corresponding Person Java object for the Person entity in the XML

@XmlType(name = "", propOrder = {
public class Person {
    private String id;
    private String name;
    public String getId() {
        return id;
    public void setId(String id) {
        this.id = id;
    public String getName() {
        return name;
    public void setName(String value) {
        this.name = value;

and a PersonList object to represent a collection of Persons. 

@XmlRootElement(name = "persons")
public class PersonList {
    private List<person> personList = new ArrayList<person>();
    public List<person> getPersons() {
        return personList;
    public void setPersons(List<person> persons) {
        this.personList = persons;

The approaches investigated were:

  • Various flavours of JAXB
  • SAX
  • DOM
In all cases, the objective was to get the entities in the XML document to the corresponding Java objects. The JAXB annotations on the Person and PersonList POJOS are used in the JAXB tests. The same classes can be used in SAX and DOM tests (the annotations will just be ignored). Initially the reference

implementations for JAXB, SAX and DOM were used. The Woodstox STAX parsing was then used. This would have been called in some of the JAXB unmarshalling tests.

The tests were carried out on my Dell Laptop, a Pentium Dual-Core CPU, 2.1 GHz running Windows 7.

Test 1 – Using JAXB to unmarshall a Java File.

public void testUnMarshallUsingJAXB() throws Exception {
    JAXBContext jc = JAXBContext.newInstance(PersonList.class);
    Unmarshaller unmarshaller = jc.createUnmarshaller();
    PersonList obj = (PersonList)unmarshaller.unmarshal(new File(filename));

Test 1 illustrates how simple the progamming model for JAXB is. It is very easy to go from an XML file to Java objects. There is no need to get involved with the nitty gritty details of marshalling and parsing.

Test 2 – Using JAXB to unmarshall a Streamsource

Test 2 is similar Test 1, except this time a Streamsource object wraps around a File object. The Streamsource object gives a hint to the JAXB implementation to stream the file.

public void testUnMarshallUsingJAXBStreamSource() throws Exception {
    JAXBContext jc = JAXBContext.newInstance(PersonList.class);
    Unmarshaller unmarshaller = jc.createUnmarshaller();
    StreamSource source = new StreamSource(new File(filename));
    PersonList obj = (PersonList)unmarshaller.unmarshal(source);

Test 3 – Using JAXB to unmarshall a StAX XMLStreamReader

Again similar to Test 1, except this time an XMLStreamReader instance wraps a FileReader instance which is unmarshalled by JAXB.

public void testUnMarshallingWithStAX() throws Exception {
    FileReader fr = new FileReader(filename);
    JAXBContext jc = JAXBContext.newInstance(PersonList.class);
    Unmarshaller unmarshaller = jc.createUnmarshaller();
    XMLInputFactory xmlif = XMLInputFactory.newInstance();
    XMLStreamReader xmler = xmlif.createXMLStreamReader(fr);
    PersonList obj = (PersonList)unmarshaller.unmarshal(xmler);

Test 4 – Just use DOM

This test uses no JAXB and instead just uses the JAXP DOM approach. This means straight away more code is required than any JAXB approach.

public void testParsingWithDom() throws Exception {
    DocumentBuilderFactory domFactory = DocumentBuilderFactory.newInstance();
    DocumentBuilder builder = domFactory.newDocumentBuilder();
    Document doc = builder.parse(filename);
    List personsAsList = new ArrayList();
    NodeList persons = doc.getElementsByTagName("persons");
    for (int i = 0; i <persons.getLength(); i++) {
        Element person = (Element)persons.item(i);
        NodeList children = (NodeList)person.getChildNodes();
        Person newperson = new Person();
        for (int j = 0; j < children.getLength(); j++){
            Node child = children.item(i);
            if (child.getNodeName().equalsIgnoreCase("id")) {
            } else if (child.getNodeName().equalsIgnoreCase("name")) {

Test 5 – Just use SAX Test 5 uses no JAXB and uses SAX to parse the XML document. The SAX approach involves more code and more complexity than any JAXB approach. The Developer has to get involved with the parsing of the document.

public void testParsingWithSAX() throws Exception {
    SAXParserFactory factory = SAXParserFactory.newInstance();
    SAXParser saxParser = factory.newSAXParser();
    final List<person> persons = new ArrayList<person>();
    DefaultHandler handler = new DefaultHandler() {
        boolean bpersonId = false;
        boolean bpersonName = false;
        public void startElement(String uri, String localName,String qName,    Attributes attributes) throws SAXException {
     if (qName.equalsIgnoreCase("id")) {
                bpersonId = true;
                Person person = new Person();
            } else if (qName.equalsIgnoreCase("name")) {
                bpersonName = true;
        public void endElement(String uri, String localName, String qName) throws SAXException {
        public void characters(char ch[], int start, int length) throws SAXException {
     if (bpersonId) {
                String personID = new String(ch, start, length);
                bpersonId = false;
                Person person = persons.get(persons.size() - 1);
            } else if (bpersonName) {
                String name = new String(ch, start, length);
                bpersonName = false;
                Person person = persons.get(persons.size() - 1);
    saxParser.parse(filename, handler);

The tests were run 5 times for 3 files which contain a collection of Person entities. The first first file contained 100 Person entities and was 5K in size. The second contained 10,000 entities and was 500K in size and the third contained 250,000 Person entities and was 15 Meg in size. In no cases was any XSD used, or any validations performed. The results are given in result tables where the times for the different runs are comma separated.


The tests were first run using JDK 1.6.26, 32 bit and the reference implementation for SAX, DOM and JAXB shipped with JDK was used.

Unmarshall Type100 Persons time (ms)10K Persons time (ms) 250K Persons time (ms)
JAXB (Default) 48,13, 5,4,478, 52, 47,50,501522, 1457, 1353, 1308,1317
JAXB(Streamsource)11, 6, 3,3,244, 44, 48,45,431191, 1364, 1144, 1142, 1136
JAXB (StAX)18, 2,1,1,1111, 136, 89,91,922693, 3058, 2495, 2472, 2481
DOM16, 2, 2,2,289,50, 55,53,501992, 2198, 1845, 1776, 1773
SAX4, 2, 1,1,129, 34, 23,26,26704, 669, 605, 589,591

JDK 1.6.26 Test comments

  1. The first time unmarshalling happens is usually the longest.

  2. The memory usage for the JAXB and SAX is similar. It is about 2 Meg for the file with 10,000 persons and 36 – 38 Meg file with 250,000.  DOM Memory usage is far higher.  For the 10,000 persons file it is 6 Meg, for the 250,000 person file it is greater than 130 Meg. 
  3. The performance times for pure SAX are better. Particularly, for very large files.

The exact same tests were run again, using the same JDK (1.6.26) but this time the Woodstox implementation of StAX parsing was used.

Unmarshall Type100 Persons time (ms)10K Persons time (ms) 250K Persons time (ms)
JAXB (Default) 168,3,5,8,3294, 43, 46, 43, 422055, 1354, 1328, 1319, 1319
JAXB(Streamsource)11, 3,3,3,443,42,47,44,421147, 1149, 1176, 1173, 1159
JAXB (StAX)30,0,1,1,067,37,40,37,371301, 1236, 1223, 1336, 1297
DOM103,1,1,1,2136,52,49,49,501882, 1883, 1821, 1835, 1822
SAX4, 2, 2,1,131,25,25,38,25613, 609, 607, 595, 613

JDK 1.6.26 + Woodstox test comments

  1. Again, the first time unmarshalling happens is usually proportionally longer.

  2. Again, memory usage for SAX and JAXB is very similar. Both are far better

    than DOM.  The results are very similar to Test 1.

  3. The JAXB (StAX) approach time has improved considerably. This is due to the

    Woodstox implementation of StAX parsing being used.

  4. The performance times for pure SAX are still the best. Particularly

    for large files.

The the exact same tests were run again, but this time I used JDK 1.7.02 and the Woodstox implementation of StAX parsing.

Unmarshall Type100 Persons time (ms)10,000 Persons time (ms) 250,000 Persons time (ms)
JAXB (Default) 165,5, 3, 3,5611,23, 24, 46, 28578, 539, 511, 511, 519
JAXB(Streamsource)13,4, 3, 4, 343,24, 21, 26, 22678, 520, 509, 504, 627
JAXB (StAX)21,1,0, 0, 0300,69, 20, 16, 16637, 487, 422, 435, 458
DOM22,2,2,2,2420,25, 24, 23, 241304, 807, 867, 747, 1189
SAX7,2,2,1,1169,15, 15, 19, 14366, 364, 363, 360, 358

JDK 7 + Woodstox test comments:

  1.  The performance times for JDK 7 overall are much better.   There are some anomolies – the first time the  100 persons and the 10,000 person file is parsed.
  2. The memory usage is slightly higher.  For SAX and JAXB it is 2 – 4 Meg for the 10,000 persons file and 45 – 49 Meg for the 250,000 persons file.  For DOM it is higher again.  5 – 7.5 Meg for the 10,000 person file and 136 – 143 Meg for the 250,000 persons file.

Note: W.R.T. all tests

  1. No memory analysis was done for the 100 persons file. The memory usage was just too small and so it would have pointless information.

  2. The first time to initialise a JAXB context can take up to 0.5 seconds. This was not included in the test results as it only took this time the very first time. After that the JVM initialises context very quickly (consistly < 5ms). If you notice this behaviour with whatever JAXB implementation you are using, consider initialising at start up.
  3. These tests are a very simple XML file. In reality there would be more object types and more complex XML. However, these tests should still provide a guidance.


  1. The peformance times for pure SAX are slightly better than JAXB but only for very large files. Unless you are using very large files the performance differences are not worth worrying about. The progamming model advantages of JAXB win out over the complexitiy of the SAX programming model.  Don’t forget JAXB also provides random accses like DOM does. SAX does not provide this.

  2. Performance times look a lot better with Woodstox, if JAXB / StAX is being used.
  3. Performance times with 64 bit JDK 7 look a lot better. Memory usuage looks slightly higher.

Reference: JAXB, SAX, DOM Performance from our JCG partner Alex Staveley at the Dublin’s Tech Blog .

Related Articles :

Related Whitepaper:

Bulletproof Java Code: A Practical Strategy for Developing Functional, Reliable, and Secure Java Code

Use Java? If you do, you know that Java software can be used to drive application logic of Web services or Web applications. Perhaps you use it for desktop applications? Or, embedded devices? Whatever your use of Java code, functional errors are the enemy!

To combat this enemy, your team might already perform functional testing. Even so, you're taking significant risks if you have not yet implemented a comprehensive team-wide quality management strategy. Such a strategy alleviates reliability, security, and performance problems to ensure that your code is free of functionality errors.Read this article to learn about this simple four-step strategy that is proven to make Java code more reliable, more secure, and easier to maintain.

Get it Now!  

Leave a Reply

eight − = 2

Java Code Geeks and all content copyright © 2010-2014, Exelixis Media Ltd | Terms of Use
All trademarks and registered trademarks appearing on Java Code Geeks are the property of their respective owners.
Java is a trademark or registered trademark of Oracle Corporation in the United States and other countries.
Java Code Geeks is not connected to Oracle Corporation and is not sponsored by Oracle Corporation.

Sign up for our Newsletter

15,153 insiders are already enjoying weekly updates and complimentary whitepapers! Join them now to gain exclusive access to the latest news in the Java world, as well as insights about Android, Scala, Groovy and other related technologies.

As an extra bonus, by joining you will get our brand new e-books, published by Java Code Geeks and their JCG partners for your reading pleasure! Enter your info and stay on top of things,

  • Fresh trends
  • Cases and examples
  • Research and insights
  • Two complimentary e-books