No, your selectors are not equivalent. The xpath "//*[contains(@class,
'template-section-view')]" matches any element with 'template-section-view'
in the class. That could be  or equally

The reason it is so slow is that every single rule you have is testing that
there is any element in the page with that class. Those are body classes and
you should be restrict them to the body element where they appear, i.e.:

This should reduce your XSLT execution time by two orders of magnitude.

Thanks Hector and Laurence for this thread.

We had the same problem, and re-writing our if-content selectors brought page load time down from 42 to 7 seconds.

Laurence, transformIterable is called many times, as in Hector's case. You mentioned before it should be called only onze on each request, do you still think having many calls is wrong?

Kees

_______________________________________________
Setup mailing list
[email protected]
https://lists.plone.org/mailman/listinfo/plone-setup

Reply via email to