[TYPO3-dev] Performance improvement: caching of MENUDATA

Steffen Gebert steffen at steffen-gebert.de
Sun Dec 20 19:32:24 CET 2009


Am 20.12.2009, 13:56 Uhr, schrieb Ralf Hettinger <ng at ralfhettinger.de>:

> I'm just performance tuning a site which uses extensive HMENUs (expAll=1
> down some levels on a large tree) and it turns out that menu generation
> takes quite a lot time (just to clarify: this of course affects only
> sites not coming from page cache. After being cached once, all is good).
>
> After having a closer look at
> typo3/sysext/cms/tslib/class.tslib_menu.php and taking times here and
> there it turned out, that too much time is spent by storing single menu
> items into cache table (MENUDATA entries).
>
> So I just turned off this storage into cache - and voila: this works
> just like a charm here, each item gets a speedup of factor ~10 (!)
>
> I just wondered if you had similar experiences or what possible side
> effects I'm overseeing: it's my impression that MENUDATA caching may be
> obsolete with more current PHP/TYPO3 versions, since the process of
> accessing database for reading (or even worse: storing) MENUDATA into
> cache takes longer than just generating the menu. At least I would think
> that this item caching should be made configurable, an example follows.

Sounds interesting - I also noticed some time ago that MENUDATA fills up  
our cache_hash (currently 87398 of 88410 entries).

Seems like this cache more hurts than it helps.

Steffen




More information about the TYPO3-dev mailing list