We are running a large installation of Piwik. Tracking approaching 700 sites, relatively low traffic individually.
We have archive script running successfully, until recently we've had no problems wit this, and all running smoothly. In the last few months we've noticed the Archive_blob report tables have become very large, despite no corresponding increase in traffic.
- As an example, in May we tracked
Total: 570779 visits, 2747116 pageviews
resulting in the following archive table with total size 1.3G
archive_blob_2013_05 1.1 G 159 M 1155463 1.3 G
- In June thus far (as at 26th june) we have tracked
Total: 450520 visits, 2057853 pageviews
resulting in the following archive table with total size 7G
archive_blob_2013_06 6.3 G 751.9 M 6882319 7 G
January this year was an even more extreme anomoly in the same respect, we tracked...
Total: 202093 visits, 776893 pageviews
resulting in a vast archive table taking up 19.2GB
archive_blob_2013_01 17.2 G 2.1 G 22422061 19.2 G
How can 776,893 page views result in an archive of 19.2 GB in January, but in May nearly 4 times the traffic 2747116, results in an archive of only approx 5% of the size.
Anyone have any ideas on why the report archival process is producing such vast Archive tables. It's filling Hard disk space allocated rapidly. We've tried removing the report tables affected in the vain hope there was some sort of temporary issue, but they are recreated (as would be expected) at the same size.
Really appreciate any thoughts!
We have archive script running successfully, until recently we've had no problems wit this, and all running smoothly. In the last few months we've noticed the Archive_blob report tables have become very large, despite no corresponding increase in traffic.
- As an example, in May we tracked
Total: 570779 visits, 2747116 pageviews
resulting in the following archive table with total size 1.3G
archive_blob_2013_05 1.1 G 159 M 1155463 1.3 G
- In June thus far (as at 26th june) we have tracked
Total: 450520 visits, 2057853 pageviews
resulting in the following archive table with total size 7G
archive_blob_2013_06 6.3 G 751.9 M 6882319 7 G
January this year was an even more extreme anomoly in the same respect, we tracked...
Total: 202093 visits, 776893 pageviews
resulting in a vast archive table taking up 19.2GB
archive_blob_2013_01 17.2 G 2.1 G 22422061 19.2 G
How can 776,893 page views result in an archive of 19.2 GB in January, but in May nearly 4 times the traffic 2747116, results in an archive of only approx 5% of the size.
Anyone have any ideas on why the report archival process is producing such vast Archive tables. It's filling Hard disk space allocated rapidly. We've tried removing the report tables affected in the vain hope there was some sort of temporary issue, but they are recreated (as would be expected) at the same size.
Really appreciate any thoughts!