Hi,
There is some documentation on this? I mean how it works, what it does, how, when, etc?
Since the beginning fo our use of piwik, now matomo, that this was the major issue. It is almost as heavy as MySQL that supports all queries and data and use almost as system resources as MySQL does, not talking about the time that it takes to process the week and month data (year, forget it, “is stopped”).
For instance, why does week use by default lastN=260 and month lastN=50? Why we look at 260 weeks and 50 months? Why not lastN=1 (the same as passing --force-date-last-n=1 to it)?
Another one: does week use the already archived data for day? And the month for day and week? The same for year using month, week and day archived data? If not, imagine that in our matomo configuration only keep log_* data for 15 days and some month archive have failed for… 7 days? The month data wil never be complete because since the fail and the re-beginning of the archive process wil have at least 7 days of “empty data”. Why not use the already processed data from the archive_* tables for the perid bellow it (as said, week will use day, month will use week and day, etc)?
This and some other questions can’t find echo in any documentation or forum post and we are willing to help not only try to make core:archive and all archiving process better and try to explain it too. Even with debug and the more verbose level available the not so much output that can help the users to understand it.
The errors too are somewhat generic (“MySQL has gone away” or “Error while sending QUERY packet”) that can link the issues to memory used by php or netwok issues linking to MySQL server or even max_allowed_packet exaustion on MySQL my.ini configuration.
Hope to ear from you!
Greetings, Pedro
So if you have these questions and more, it would be useful if you can create a ticket on github and suggest us to improve the doc at: