0

I've inherited an EE site that has a tag cache problem. The tag cache is grows rapidly and seems to be accelerating in its rate of growth recently.

The problem this presents is that the tag cache can grow so large at times that when EE needs to clear it, it actually takes so long the whole process times out leaving a white screen (the error is a timeout).

It's so bad that, despite a routine that we run that should clear the cache on weekdays, 3 times per day, over the weekend it can grow to over 5GB in size!

I have an inkling that it's a combination of web spiders (e.g. Google bot) and the weird and wonderful setup that this site has (essentially using some templates as front-controllers for subsections of the site).

I guess somewhere along the line, something is probably creating an endless tree of URLs that are being spidered and this is resulting in the massive cache.

This is just not right and I wondered if anyone else has experienced similar issues with the tag cache and how they overcame it.

4
  • Turn it off or alternatively set the cache timeout to 30 minutes or less. Be nice to see some code where it's being used too. – stuartmcd69 Apr 14 '16 at 12:38
  • Have you an example of the parameters that are being used like cache="yes" refresh=“10” and anything thing else that helps context? EE2 I take it? – John Henry Donovan Apr 14 '16 at 13:13
  • @stuartmcd69 when you say 'turn it off' do you mean remove the cache="yes" in all cases? Or is there a global override? – simonhamp Apr 14 '16 at 13:29
  • @JohnHenryDonovan yep EE2. there are over one hundred tag cache references and the refresh rates are 1|30|60|180|300|1440. The most common is by far '180' – simonhamp Apr 14 '16 at 13:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Browse other questions tagged or ask your own question.