Laurence Rowe wrote > > > khink wrote >> >>> 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.: >> >> 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. >> Do you still think this is wrong? >> > > Is this the time taken for the single request to fetch the HTML, or > including all CSS/JS/images etc? How long does an unthemed page load take? > > transformIterable does need to be called every request as it makes the > decision whether to theme or not. Looking at it again, it seems to be > doing a bit too much work in that case (attempting to parse the response > before looking at the content type header). I'll fix that. > > Laurence > > transformIterable has to be called every request because it makes the > decision whether a response needs theming or not. Most of the time it just > passes >
I responded too soon, parseTree doesn't attempt to parse anything that is not text/html so it's only unthemed html that gets parsed unnecessarily. Laurence -- View this message in context: http://plone.293351.n2.nabble.com/huge-performance-issues-using-Diazo-tp7372056p7421037.html Sent from the Installation, Setup, Upgrades mailing list archive at Nabble.com. _______________________________________________ Setup mailing list [email protected] https://lists.plone.org/mailman/listinfo/plone-setup
