Saxon

Legacy ID: #4519152 Legacy Poster: Michael Kay (mhkay)

It's easy to nominate a different XML parser when you invoke Saxon via the Java API, for example you can call Configuration.setSourceParser(), or you can supply a SAXSource as input in which the XMLReader has been set by the application to the parser of your choice. There's no particular reason this option isn't offered in the XQuery command line. However, you shouldn't normally try to test Saxon performance by running from the command line. Your figures will be heavily distorted by the time taken to load the Java VM, which in turn depends heavily on what other applications are running on your machine at the time. It's best to write a Java application to do it, and ensure that it runs the query repeatedly for at least a couple of minutes; it's also best to ignore the first few executions whose performance tends to be very unpredictable from one run to the next. I don't think that you'll find that the choice of XML parser has a major effect on performance, unless you choose one that is unusually bad - but by all means measure it and tell me what you find out. Michael Kay http://www.saxonica.com/