Closed wdebusschere closed 4 years ago
If you do not purge it, yes it is. How often do you run the cron job ?
cron job every hour.. but doesn't change nothing.. also running it manually doenst make the size of the db less
| sym_cachelite_references | | Browse | Structure | Search | Insert | Empty | Drop | 1,211,682 | MyISAM | utf8_unicode_ci | 526.2 MiB
table sym_cachelite_invalid is always empty..
@wdebusschere DO you have many many pages (url) on that site ? If so, this is expected... In order to be able purge the cache when editing entries, we need to create a different entry for each entry/section used for each url. I do have sites with 2Gb of data in this table.
Also: do you use many query strings ? This also makes the url different, so maybe you are getting a lot cache hit ratio.
Finally, what is your concern ? Is it speed ? Size on disk ?
@nitriques Thanks for the reply. Ok, so big database is normal. This is a problem as we only got 1GB db's. So i have disabled the storing in the database and the cache expires eventually. If some new data gets added or updated we have created a delete all cache button, which is better in our situation, then to have long delays saving and deleting the cache.
The thing is, it is sometime due to some entries being present on ALL pages (like the menus/footer) that will get the data so big. Maybe we should consider "excluding" some section from this behavior.
Symphony 2.7.7 Cachelite 2.1.2
'clean-strategy' => 'cron',