XML.orgXML.org
FOCUS AREAS |XML-DEV |XML.org DAILY NEWSLINK |REGISTRY |RESOURCES |ABOUT
OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]
Re: [xml-dev] Re: The Goals of XML at 25, and the one thing that XMLnow needs

And now I seem to recall that MS had some condition on use that people could not publish benchmarks of MSXML, which makes that part of my comment unfair. I think some people published a benchmark with a mussing name for that product. But the memory is not strong...

As for Xerces/Java performance, this paper https://www.researchgate.net/publication/220787871_The_XMLBench_Project_Comparison_of_Fast_Multi-platform_XML_libraries  suggests that, at that time, only the Oracle libraries were worse, of the major tools.  (On the other hand, there are some benchmarks with different results, and it often depends on the kind of markup your benchmark has, and for XSLT the parsing is usually not the major contributor to performance anyway.)

So let me rephrase: in order make to a legimate comparison of a new parse method, it is necessary not just to pick a couple of parsers you consider typical or median or popular. It is better to show the best and worst two plus whatever parser is most often found in other papers: if you have a four-fold improvement over a mediocre but popular parser, and it turns out there are several other parsers that offer a ten-fold improvement, it changes what may be concluded by the reader about your method.

Cheers
Rick

On Fri, 23 Jul. 2021, 14:21 Mukul Gandhi, <mukulg@softwarebytes.org> wrote:
On Thu, Jul 22, 2021 at 8:52 PM Rick Jelliffe <rjelliffe@allette.com.au> wrote:

In previous decades, as I read these kinds of papers and came up to these omission sections, my reaction was to doubt that the method was in fact practical. (Benchmarking against Xerces, the slowest  parser, did not help, either: how it compares to MSXML is more compelling.)

I don't think that, Xerces is the slowest XML parser. Our measurements show that, its quite a performant XML parser for various production scenarios. Also, Xerces and JDK share the same XML implementation code base.

But I'd also agree that, MSXML should be faster on windows systems, since its available as native platform code.
 

--
Regards,
Mukul Gandhi


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index]


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 1993-2007 XML.org. This site is hosted by OASIS