There is this config setting that allows specific date ranges to be pre-processed for specific date ranges (I.e. specific date ranges, or periods such as
last90 etc.): https://github.com/matomo-org/matomo/blob/35957fc5aeecf9f6f795e4e8e005f9d37fab7a2d/config/global.ini.php#L377-L380
However, this config setting doesn't seem to work to pre-process the
All Websites dashboard for the specified Date Ranges.
@Starker3 I'm not sure there is current any archiving of multi-site data, the datatables for the sites appear to be loaded and merged on demand to create the all website view.
To support pre-processing of multi-site data the multi-sites plugin would need to be enhanced with it's own archiving processor to write the merged sites data to an archive.
This could provide a performance benefit in some circumstances but could also increase the load on the archiving processes.
@bx80 Do you know if the datatables that are loaded when the all websites dashboard is loaded is getting data from the already archived periods?
I don't know if its worth the effort to implement some sort of multi-set pre-processing as long its its able to load the pre-processed reports for the period selected.
(I.e. is it currently treating a date range report the same way it would for a date range that isn't yet processed even if the individual sites already have those periods processed?)
@Starker3 Existing numeric archives are loaded individually for each site and then merged into a single datatable. From what I can see, if there are existing archives for the requested date range for all the sites then they should be used.
It's worth noting that previous period data tables are also loaded for the all websites dashboard, so if there are 10 sites then 2 x 10 archives would be loaded and merged into two datatables. I'm not sure what would happen trying to get the previous period of
last90, this might cause (slow) archiving of that date range.
It would probably take a bit of time to investigate this in more detail.