cache_advagg_info is at 2.4 gigs? My first instinct was to empty but I wanted to post the issue. This is not a large site so no table should be THAT high. Any suggestions on what may be going on? If this is not module related what could push the table up that high.
I noticed at admin/config/development/performance/advagg/operations an option to flush and also the drastic measures below that.
My questions are:
Why would it grow so large?
Should I use the flush option?
Should I empty just cache_advagg_info in phpadmin?
Am I missing something or should flushing be a regular maintenance task?
Thanks, this has proven to be an excellent module otherwise.

CommentFileSizeAuthor
#7 advagg-2114545-7-cache-jsmin-1-day.patch1.75 KBmikeytown2
Support from Acquia helps fund testing for Drupal Acquia logo

Comments

thedosmann’s picture

thedosmann CreditAttribution: thedosmann commented

Use of cache option at admin/config/development/performance/advagg/operations had no effect. Looking at cache_advagg_info it looked as if an empty would not cause any ill effects so I emptied the table and the world didn't end. I'm going to keep an eye on this but my previous questions apply. Something caused this fellow to get real fat.

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented
Category: support » task

I'll see what is causing this. My guess is the advagg_js_compress sub module.

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented
Category: task » bug
thedosmann’s picture

thedosmann CreditAttribution: thedosmann commented

Update: Since using empty on table yesterday the table, cache_advagg_info, has grown to 96 mb. This is disproportional and not what would be expected.
I'll probably end up emptying the table every 2-3 days. If I can provide any info let me know. It looks like something is not making it into the cache cleaning arsenal but I've not looked into the code any. Perhaps an array that didn't pick up something? Just throwing that out there.
Thanks for looking at this.

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented

Could you give me the output from this query?

SELECT 
  SUBSTRING(cid, 1, (6 + LOCATE(':',  SUBSTRING(cid, 8)))) AS primary_key,
  count(*) as counter
FROM cache_advagg_info
GROUP BY (primary_key)
thedosmann’s picture

thedosmann CreditAttribution: thedosmann commented 
primary_key counter
advagg:db 110
advagg:file 158
advagg:js_compress 40301
mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented
Status: Active » Needs review
FileSize
advagg-2114545-7-cache-jsmin-1-day.patch1.75 KB

Could you test this out?

thedosmann’s picture

thedosmann CreditAttribution: thedosmann commented
Status: Needs review » Active

After applying patch and running update

advagg_js_compress module

7201 - Clear the cache_advagg_info cache. Implements hook_update_N().

After update ran

The following updates returned messages

advagg_js_compress module

Update #7201
Cleared the cache_advagg_info cache of js_compress entries.

Watchdog is reporting

Parse error: Missing operand in file '[inline]' on line 1
var islrsharing = true; var islrsocialcounter = true;var hybridsharing = true;

Advise

thedosmann’s picture

thedosmann CreditAttribution: thedosmann commented

I checked the config again and unticked

INLINE COMPRESSION: USE EVEN IF THIS PAGE IS NOT CACHEABLE

This got rid of the Parse error

Everything is running OK ; No watchdog errors and status is OK, and no console errors. I'll watch the table and should know in 24 hours if this worked for sure.

thedosmann’s picture

thedosmann CreditAttribution: thedosmann commented

28mb

primary_key counter
advagg:db 78
advagg:file 152
advagg:js_compress 6011
mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented

Things still look good after the weekend?

thedosmann’s picture

thedosmann CreditAttribution: thedosmann commented

Yes, it seems to be good. Thanks for your help on this.

mikeytown2’s picture

mikeytown2 CreditAttribution: mikeytown2 commented
Status: Active » Fixed

Awesome :)
Patch in #7 has been committed.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.