[Home] [By Thread] [By Date] [Recent Entries]

  • To: xml-dev@l...
  • Subject: Re: XML-enabled databases, XQuery APIs
  • From: Ronald Bourret <rpbourret@r...>
  • Date: Mon, 18 Apr 2005 22:07:36 -0700
  • In-reply-to: <200504181843.j3IIhFvI097554@w...>
  • References: <200504181843.j3IIhFvI097554@w...>
  • User-agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 Netscape/7.1 (ax)

I'm neutral here, but for an opposing view see "XML Parsing: A Threat to 
Database Performance" [1] by Matthias Nicola of IBM. From the abstract:

"XML parsing is generally known to have poor performance characteristics 
relative to transactional database processing. Yet, its potentially 
fatal impact on overall database performance is being underestimated. We 
report real-word database applications where XML parsing performance is 
a key obstacle to a successful XML deployment..."

-- Ron

[1] 
http://lists.w3.org/Archives/Public/www-ws/2004Oct/att-0032/MNicola_CIKM_2003_1_.pdf

Michael Kay wrote:
> I would be very surprised if XML parsing contributes anything noticeable to
> the cost of a database load (in shredding mode). Except possibly for a
> pathological XML document containing 3 nodes and 3 billion bytes.
> 
> I haven't looked at the latest products from MS or Oracle, but my experience
> of database loading with complex data and a realistic level of indexing is
> that it's a couple of orders of magnitude slower than XML parsing. You can
> improve that with a custom loader that bypasses SQL and does a lot of
> heavy-duty sorting and merging to minimize head movement on the disk (does
> anyone still do that?), but I think it's still true that the parsing cost is
> immaterial.


Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member