You can clone with
HTTPS or Subversion.
The purge old temporary archives is probably not run on every table once in a while. Some tables are huge, wasting a lot of valuable mysql DB space (especially for shared hosts where this is a real problem).
piwik_archive_blob_2011_10 4.6 M 1.4 Gb 144.9 Mb 1.6 Gb ```
But there are others: The one for Jan 2012 seems a bit big too, maybe temporary yearly reports not purged? Same for Jan 2011, 3-4 times bigger normal table, and for Jan-Feb 2008.
* It also appears that the archive_numeric are not purged neither. These are huge it hurts.
Why would August 2008 numeric table for the demo has 119,800 records?
We should check WHY this data is not purged yet. This will free a lot of space and will make everyone very happy!
This was also reported in forum specifically for the Janauary table -- maybe yearly reports are not deleted correctly. Especially reports with timing out memory/incomplete?
See also the bug reported in forum: over-deletion of temporary data
(In ) Fixes #3003
This will result in much disk space currently wasted being deleted the first time the new scheduled task runs after update!
(In ) Refs #3003 Enable task