Subject: Re: [xsl] Processing milestoned XML leads to many preceding:: calls and horrible performance From: Michael Kay <mike@xxxxxxxxxxxx> Date: Tue, 21 Feb 2012 10:28:05 +0000 |
There are quite a few things that can be done to improve your XSLT code, as Andrew has pointed out; especially if you move to an XSLT 2.0 processor. But the problem is not a superficial coding problem, it's the basic algorithmic design. Looking at that horrendous XPath expression
The problem is (I think) in both <vers/> (that's "verse" in Czech) and <kap/> (that's an abbreviation of "chapter") are just milestones, so I have to go through all verses in whole book all the time (yes, this is http://www.joelonsoftware.com/articles/fog0000000319.html all over again).
Any ideas? Would some other XSLT processors other than xsltproc (libxml 20706, libxslt 10126 and libexslt 815) I am using be able to optimize this somehow?
Thanks a lot,
MatDj
Michael Kay Saxonica
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Processing milestoned XML, Tony Graham | Thread | Re: [xsl] Processing milestoned XML, Alex Muir |
Re: [xsl] Processing milestoned XML, Tony Graham | Date | Re: [xsl] Processing milestoned XML, Matěj Cepl |
Month |