Re: Archive Blob tables suddenly got very big, out of relation to traffic increases

Thanks for your reply.

The DBStats plugin is installed and is how we are getting the reported stats on data usage. This doesn't give visibility beyond the table sizes, or into the monhtly usage within the tracking tables.

The key problem is the archive tables generated are vastly inflated, and crippling the disk usage. For 776,893 pageviews in January of this year, the archive table generated is 19.2GB. This contrasts with 2,747,116 pageviews in May, resulting in an archive table of just total size 1.3G. This means the archive requirement (based on archive size per page view) is in the region of 4,500% greater from one month to another, it's such a vast anomoly that something is clearly going seriously awry. Presumably I should be looking at another metric than page views or visit to see where this extra data is coming from.

Just not sure how to get visibility on what is causing the Archive table itself to be so inflated, I've tried to look through the data but it's proving very difficult to isolate where all this extra data is coming from.