Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xml-dev] XML Performance in a Transacation and recursion

From: Rick Marshall <rjm@-------.--->
To: Peter Hunsberger <peter.hunsberger@-----.--->
Date: 4/2/2006 11:58:00 PM
i've found the performance problem, and it ties together with the 
discussion on recursion.

here's the problem - the stylesheet vocabulary is used to write a 
postscript program. but postscript strings can't contain '(' or ')' (the 
delimiters for a postscript string).

so every output string has to be parsed and the parentheses escaped with 
a '\'.

we have no control over the source of the documents so i tried the 
recursive examples for substituting one string with another through a 
string. eg "ABC(DEF" ends up as "ABC\(DEF" and "AB(DEF)GHI()JK(" ends up 
as "AB\(DEF\)GHI\(\)JK\(".

i've solved my performance problem for the moment by preprocessing the 
input with sed instead.

but i'm not happy because sed has no knowledge of the dom and blindly 
applies the transformation, instead of only applying it to the content 
of elements.

so here's a real challenge - write a template for the above 
transformation with an example on how to call it; i'll put it into the 
style sheet and test it against the examples and we'll find out what 
techniques are linear or better and what ones aren't.

the solution (in this case) must work with xsltproc.

currently on a 410k input document 41 of the 43 seconds of processing 
time is taken up by the string escaping function.

writers of xsl processors can then compare their performance results 
over the various techniques as well.

regards

rick

Peter Hunsberger wrote:

>On 3/26/06, Rick Marshall <rjm@z...> wrote:
>  
>
>>Michael Kay wrote:
>>
>>    
>>
>>>>o(n2) is what you get when something is wrong.
>>>>
>>>>        
>>>>
>>>No, there are many problems for which no solution exists that is better than
>>>O(n^2) - in any language.
>>>
>>>
>>>      
>>>
>>and it's a problem, because those problems can't be scaled, but instead
>>have to be tackled by decomposition (at least you then get linear response)
>>
>>    
>>
>
>Think about what you're saying here:  if you can break the data apart
>by hand and  get linear processing times you've demonstrated that
>there is an algorithm that has linear processing times. The issue is
>coding it up...
>
>--
>Peter Hunsberger
>
>
>!DSPAM:44280618321021679284069!
>
>  
>


begin:vcard
fn:Rick  Marshall
n:Marshall;Rick 
email;internet:rjm@z...
tel;cell:+61 411 287 530
x-mozilla-html:TRUE
version:2.1
end:vcard


transparent
Print
Mail
Like It
Disclaimer
.

These Archives are provided for informational purposes only and have been generated directly from the Altova mailing list archive system and are comprised of the lists set forth on www.altova.com/list/index.html. Therefore, Altova does not warrant or guarantee the accuracy, reliability, completeness, usefulness, non-infringement of intellectual property rights, or quality of any content on the Altova Mailing List Archive(s), regardless of who originates that content. You expressly understand and agree that you bear all risks associated with using or relying on that content. Altova will not be liable or responsible in any way for any content posted including, but not limited to, any errors or omissions in content, or for any losses or damage of any kind incurred as a result of the use of or reliance on any content. This disclaimer and limitation on liability is in addition to the disclaimers and limitations contained in the Website Terms of Use and elsewhere on the site.

.
.

transparent

transparent