[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

RE: XML Performance in a Transacation

• To: "'Rick Jelliffe'" <rjelliffe@a...>,<xml-dev@l...>
• Subject: RE: XML Performance in a Transacation
• From: "Michael Kay" <mike@s...>
• Date: Fri, 24 Mar 2006 08:34:31 -0000
• In-reply-to: <442399D1.1000209@a...>
• Thread-index: AcZPEUD9JYSTdaCkTTKrdpfxW2PwsAAC70DQ

> On your issue of N(O^2), I think Rick is referring to a potential 
> problem of XML-to-Tree implementations, or maybe XPath etc 
> traversers, 
> rather than XML-to-stream processors necessarily.


Tree builders aren't O(n^2). They are essentially linear until you run out
of memory, at which point they go exponential. In principle you can solve
that problem by more effective use of secondary storage, but again it's a
case where the number of people who need it isn't enough to stimulate the
investment. It's cheaper to buy more memory.

XSLT processing isn't O(n^2) either. Many transformations run in linear
time. Of course it's very easy for a user to write XSLT applications that
are O(n^2) or worse - and it would be wrong to make it difficult!

Michael Kay
http://www.saxonica.com/

• References:
  • Re: XML Performance in a Transacation
    • From: Rick Jelliffe <rjelliffe@a...>

• Prev by Date: RE: XML Performance in a Transacation
• Next by Date: Re: XML Performance in a Transacation
• Previous by thread: Re: XML Performance in a Transacation
• Next by thread: Re: XML Performance in a Transacation
• Index(es):
  • Date
  • Thread