You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks to db sessions and using redis for cache my Matomo instance loads really quick and feels quite fast to interact with.
But every time I open the administration-homepage (which is quite often), all widgets load nearly immediately from cache, but the getSystemCheck takes more than 5 seconds most of the time.
I assume this is because it runs all system checks (and therefore e.g. reads the hash of all files) every time.
In addition if you click on an item in the navigation bar before the request has finished (which is most of the time). It will be immediatly replaced with the bright red Oops… there was a problem during the request. box until the next page has finished loading (but I guess this is a seperate bug)
I guess caching the system check results on the details page can make debugging frustration, but maybe the results can be cached for the small widget (and maybe show a last checked 5 minutes ago or something like this)
The text was updated successfully, but these errors were encountered:
Just a random thought:
Thanks to db sessions and using redis for cache my Matomo instance loads really quick and feels quite fast to interact with.
But every time I open the administration-homepage (which is quite often), all widgets load nearly immediately from cache, but the
getSystemCheck
takes more than 5 seconds most of the time.I assume this is because it runs all system checks (and therefore e.g. reads the hash of all files) every time.
In addition if you click on an item in the navigation bar before the request has finished (which is most of the time). It will be immediatly replaced with the bright red
Oops… there was a problem during the request.
box until the next page has finished loading (but I guess this is a seperate bug)I guess caching the system check results on the details page can make debugging frustration, but maybe the results can be cached for the small widget (and maybe show a
last checked 5 minutes ago
or something like this)The text was updated successfully, but these errors were encountered: