I haven't been in Matomo as much recently and found it to be incredibly slow the last few times I've been in it. I did some troubleshooting and noticed the time it took to load the "All Websites" page took ~30 seconds -- the same time it takes for the archiving cron to run.
This needed to be added to the config.ini.php file:
enable_browser_archiving_triggering = 0
I thought that was in the Matomo config before, so I'm not sure when it went missing or maybe it always was... but as soon as I added in this property to the config.ini, it immediately resolved the loading time of the All Websites page.
The reference for this step came from here: https://matomo.org/faq/new-to-piwik/faq_137/ (and a related page is here: https://matomo.org/faq/on-premise/how-to-configure-matomo-for-speed/)
I also noticed (but didn't try it yet) from that page their recommendation to add this too, but not sure how important this one would be:
enable_sql_optimize_queries = 0
Also, just my two cents but the cron runs every 15 minutes... seems a little overkill IMO and could be every 30 or 60 minutes instead. That's maybe another topic though all together.
My ask... could we consider adding in the
enable_browser_archiving_triggering = 0to the config.ini.php file to improve performance since the cron is already used to generate the reports?
@d19dotca thanks for bringing this up. I also think that we can easily run the background tasks less frequently for such an anlytics tool, so for a start I have reduced it to half the time now every 30min.
enable_browser_archiving_triggeringwe usually lean towards the upstream defaults instead of optimizing for a specific use-case (in your case speed optimization) I don't know the details for this specific one, but mostly the developers have their reasons for why defaults are that way. I am glad though they have written docs on how to shape the app behavior for this use-case specifically.
@nebulon That's fair. I guess I assumed they were sort of paired together as my understanding for disabling the auto-archiving in the web part was specifically for speed gains which you guys had already done by setting up crons instead for archiving reports, so the KB I linked to seemed relevant to that assumption that we wanted Matomo to be configured for speed instead of convenience. But I can appreciate that you want to keep the amount of customizations to be as slim as possible.