Page tree is slow about flux HOT 5 CLOSED

Hi Fabien,

I'll take a look what cachegrind has to say. It could very well be an issue with caching - I'll let you know what I find :)

Cheers,
Claus

from flux.

Thanks, Claus.

While checking #92, could you also test the following action on the Bootstrap Package:

• create a new page
• delete a page
• hide a page
• create a new content
• delete a content

The same operations can be done on http://demo.typo3.org/typo3/. From my end, I notice a sensible difference of speed.

from flux.

Some progress: inheritance is related here; the page rootline is now being considered and this does add quite a bit of load.

So far I've been able to cut execution time as well as number of functions called by each ~45% by implementing one missing cache case. The internal cache seems to really save time when working with big page trees but it does require some "warming" before the benefit kicks in (which should be, I estimate, somewhere around the 2nd or 3rd page being inspected in the rootline).

I'll keep cutting here but 45% so far isn't bad at all :)

from flux.

Hi Fabien,

How is the latest git master working out on your tests? When working locally I managed to shave off a bit more than 50% of rendering time but that could very well be slower on servers with a bit of load, or faster on sites that use many templates in the page rootline (which should definitely speed up a lot more than what I noticed locally).

Hope it helps. I'm sure there is more performance to gain but if it is acceptable (somewhere around the level before the inheritance feature arrived) I think we should close this issue - and in the future perhaps reopen one when we have identified other places to optimise. What say you? :)

Cheers,
Claus

from flux.

I am seconding the performance gain. Content Elements management look faster, indeed. Creating a page in the page tree seems the slowest action for me surprisingly enough.

from flux.