Re: Diazo performance problem

On 4 February 2014 08:32, Chrissy Wainwright <chrissy-qEDqLqPM/[email protected]> wrote:

>
> This is caused by XPath calls. We've achieved some speed ups by avoiding
>  xpath expressions with // where possible.
>
>
> Also avoid css:content-children and css:theme-children, just select a
> better div or id.
>
>
> This is the first time I've heard about either of these causing speed
> issues, is it documented somewhere? I ran into the xpath one the other day,
> though I wasn't sure exactly what caused the site to slow down (I thought
> it was my particular selector).
>

For theme-children I'm fairly sure it can't be the case as it is only
evaluated on compilation.

For content-children it only adds a /node() to the xpath. If you can show a
slow down *with the same selector* then there's an alternative
implementation strategy that could be tried with an xsl:template.

Laurence

------------------------------------------------------------------------------
Managing the Performance of Cloud-Based Applications
Take advantage of what the Cloud has to offer - Avoid Common Pitfalls.
Read the Whitepaper.
http://pubads.g.doubleclick.net/gampad/clk?id=121051231&iu=/4140/ostg.clktrk

_______________________________________________
Plone-developers mailing list
Plone-developers-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/plone-developers