[TYPO3-dev] cache_hash flooded by MENUDATA

Mathias Schreiber [wmdb >] mathias.schreiber at wmdb.de
Tue Apr 21 08:15:02 CEST 2009


Patrick Gaumond schrieb:
> Steffen Gebert wrote:
> 
>> I found the hint to use clearCacheAtMidnight. But as clearing the 
>> cache takes some minutes (we also use nc_staticfilecache), I think 
>> it's not a good idea (the cache is then cleared by the first request 
>> after midnight, isn't it?).

First off, IIRC this sets the TTL of the cache to 0001hrs of the next day.
Thus the first hit after mightnight on page X will trigger the new 
generation of page X - not all pages in the installation.

> Get inspiration from this extension that use TRUNCATE instead of DELETE:

should be core anyways, but thats another story :)

> http://typo3.org/documentation/document-library/extension-manuals/truncate_cache/2.0.0/view/1/1/#id4213529 
> 
> 
> See if you can adapt it for clearCacheAtMidnight instead of the BE menu...

Generally a good idea, but I think the main problem is that deleting the 
cache takes a lot of time (which might be caused by the rather big cache 
tables AND a lot of static pages being generated).

Practically, there is no solution right now, since truncate cannot be 
used because AFAIK nc_staticfilecache needs the "row-by-row" type of 
cache deletion to delete its rendered files.

But what you could do is to "truncate" nc_staticfilecache as well.
So if the command gets called, first truncate the cache tables and then 
issue an rm -rf [your_static_filecache_directory] and see, if it's faster.

hope this helps
cheers
Mathias




More information about the TYPO3-dev mailing list