August 22, 2015 in Technical Problems
I have a database with 2.5 million posts and the posts table is 12GB. The core_cache table is now 50GB and growing. Is this supposed to be like this or is it a bug?
Please submit a ticket for further investigations.
We have found some scenarios where truncating the cache table could fail, so I'd really like to take a further look at this to see if it's something new or if it will be resolved with the next release.
I had switched off my cron for sometime because of server load problems. I'm guessing the truncating is done by the cron?
I switched on cron and the cache was deleted within a couple minutes.
This topic is now archived and is closed to further replies.
Started 2 hours ago
Started 5 hours ago
Started November 29