Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
The cache_advagg_aggregates cache bin can get quite large at times. Going to see what I can do; thinking of decreasing the time between trims.
Comment | File | Size | Author |
---|---|---|---|
#10 | advagg-2730443-9-smaller-cache-items.patch | 3.51 KB | mikeytown2 |
#5 | advagg-2730443-5-inline-js-min-cache.patch | 940 bytes | mikeytown2 |
Comments
Comment #2
mikeytown2 CreditAttribution: mikeytown2 commentedJust checked and the oldest entry is 4 days ago... so this isn't a simple fix. Looking and there are some 12MB cache entries so I should be able to clean this up more.
Comment #3
dasrecht CreditAttribution: dasrecht commentedHi there, i just got into the same situation. Our cache_adgavv_aggregates table exceeded the size of 14.9 GB. Is there a value which can be tweaked to limit the size of the aggregate table?
Comment #4
mikeytown2 CreditAttribution: mikeytown2 commentedLooking into this and it appears to be caused by large inline blocks of css and/or js code. Also looks like the advagg:js_compress key does not get cleaned up. Will need to fix that.
Comment #5
mikeytown2 CreditAttribution: mikeytown2 commentedFirst step is to only cache inline js for 1 hour instead of 7 days.
Comment #7
mikeytown2 CreditAttribution: mikeytown2 commentedThis should fix most of the issues. Will look into the full render cache, if inline should not be cached.
Comment #8
mikeytown2 CreditAttribution: mikeytown2 commentedComment #10
mikeytown2 CreditAttribution: mikeytown2 commentedThis has been committed. Cache should shrink after a week or two.
Comment #12
slinky CreditAttribution: slinky commentedI much appreciate this module but I do have a concern. Our database was 600MB. After installing the module, this table alone added 505MB in over 54,000 table entries. I haven't looked into this too deeply but the heft is tremendous and I'm finding it challenging to believe that caching is being performed efficiently.
Comment #13
mikeytown2 CreditAttribution: mikeytown2 commented@slinky
The more organized your css and js is loaded on your page the smaller it will be. Order of css and js files matters. AdvAgg doesn't change the order so it has to record every permutation. So in your case you have 54k different file combinations of css and js.