Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cache system check results #14340

Open
Findus23 opened this issue Apr 11, 2019 · 0 comments
Open

cache system check results #14340

Findus23 opened this issue Apr 11, 2019 · 0 comments
Labels
c: Performance For when we could improve the performance / speed of Matomo.

Comments

@Findus23
Copy link
Member

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)

grafik

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)

@tsteur tsteur added this to the Backlog (Help wanted) milestone Apr 11, 2019
@tsteur tsteur added the c: Performance For when we could improve the performance / speed of Matomo. label Apr 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c: Performance For when we could improve the performance / speed of Matomo.
Projects
None yet
Development

No branches or pull requests

2 participants