OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

 


 

   Java SAX Speed (Was: Pushing SAX events out onto the Web?)

[ Lists Home | Date Index | Thread Index ]
  • To: xml-dev@lists.xml.org
  • Subject: Java SAX Speed (Was: Pushing SAX events out onto the Web?)
  • From: Jochen Wiedmann <joe@ispsoft.de>
  • Date: Wed, 14 Aug 2002 08:45:39 +0200 (CEST)
  • Cc: "Roger L. Costello" <costello@mitre.org>
  • User-agent: IMP/PHP IMAP webmail program 2.2.6


Hi, Roger,

I have Java classes available that

  a) Convert SAX events into a binary stream and tha
  b) convert such a binary stream into SAX events

If you are interested, I will send them to you.


Btw, that brings me to another question, which may
be of interested to Dare:

I originally wrote this classes with the idea to
replace the SAX generator with a C library. I hoped
that reading the binary stream and converting it into
SAX might be much more efficient than using a SAX
parser to read the serialized XML and converting
that into a SAX stream.

However, the result was *quite* surprising:

- Running the examples for the first time gave the
  expected result: The actual XML parser took about
  150 ms, my binary parser took 10 ms.

- Running the examples a second time (in a loop)
  changed the times to about 40 ms and 10 ms.

- And repeating the examples over and over again
  resulted in an average time of 10 ms both, the
  actual XML parser (Crimson) being indeed slightly
  faster

I though of Hotspot, but I doubt that it can speed
up an XML parser that much. And using the classic
engine didn't change matters.

Any explanations or ideas?


Regards,

Jochen




 

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

Copyright 2001 XML.org. This site is hosted by OASIS