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

Re: XML Performance in a Transacation

• To: xml-dev@l...
• Subject: Re: XML Performance in a Transacation
• From: Rick Jelliffe <rjelliffe@a...>
• Date: Fri, 24 Mar 2006 20:13:17 +1100
• In-reply-to: <69181609-8802-419D-A193-E23EB8101701@m...>
• References: <200603231325.k2NDPBG8029517@m...> <44236A54.4060302@a...> <444C61A3-72FB-44D6-9ECC-2B5839CFA713@m...> <442392BA.2070208@a...> <69181609-8802-419D-A193-E23EB8101701@m...>
• User-agent: Mozilla Thunderbird 0.6 (X11/20040502)

Wolfgang Hoschek wrote:

>
> A new performance oriented parser implementation must come with a  
> straightforward API, or else it will matter little in practise.

Yes, but how will that help Rick M's problem?

"some initial investigation reveals that the vast majority of the time 
is spent parsing the input strings and coping with utf-8."

See, what I think is happening is that instead of you saying "Yes SSE 
optimization research would be good; and better APIs would be good; and 
my expectations is that more good would come from better APIs" you seem 
to be saying "NO AMOUNT of SSE optimization is needed because the 
problem is APIs".  

Similarly, instead of saying "Yes SSE optimization research would be 
good; and better algorithms would be good; and my expectations is that 
good would come from better algorithms" Rick M seems to be saying "NO 
AMOUNT of SSE optimization is needed because the problem is algorithms".  

I don't see any reason that progress in one area would limit progress in 
others. However, the attitude of denying the need for improvements in 
one area until some pet area is adequately addressed just serves to hold 
back any improvement. Observers draw the wrong conclusion "they cannot 
even agree on the central problem, lets not go ahead" rather than "oh, 
there is potential on several fronts, lets go ahead!"  IYSWIM

That is why, ultimately, the current XML efficiency problem is not with 
technology: not APIs, algorithms, CPU instruction sets. The XML 
efficiency problem is with motivating researchers and open source 
developers into areas that match corporate business requirements. 

Cheers
Rick Jelliffe

• Follow-Ups:
  • Re: XML Performance in a Transacation
    • From: Tatu Saloranta <cowtowncoder@y...>

• References:
  • Re: XML Performance in a Transacation
    • From: Rick Jelliffe <rjelliffe@a...>
  • Re: XML Performance in a Transacation
    • From: Wolfgang Hoschek <wolfgang.hoschek@m...>
  • Re: XML Performance in a Transacation
    • From: Rick Jelliffe <rjelliffe@a...>
  • Re: XML Performance in a Transacation
    • From: Wolfgang Hoschek <wolfgang.hoschek@m...>

• 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