Home. 
.

transparent

transparent

transparent

Altova Mailing List Archives


Re: [xsl] alternative to repeatedly walking the ancestor axis in 1.0

From: "Vladimir Nesterovsky" <vladimir@-------------------->
To:
Date: 8/4/2008 1:48:00 PM
> > P.S. You seems to be obsessed with an optimization of ancestor walks.
> >
Are you sure you have a problem in the first place?
> 
> Obsessed is the
wrong word - perhaps "mildly interested" is more
> accurate - but yes I would
say it's a problem to have to walk the
> ancestor axis for every node.  Why?
It can be expensive depending on
> the tree model and it prevents potential
streaming optimisations.
> 
> And of course, when the application is large
enough and used by enough
> people, a slight performance tweak can save a lot
of money.

If ancestor walks are what the profiling shows as a bottleneck
then it's definitely worth for an attention. I wouldn't trusted to a feeling.
Besides, I think explicit optimization can harm to an optimization that engine
may perform on itself.

--
Vladimir Nesterovsky
http://www.nesterovsky-bros.com/


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