-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
MariaDB doesn't use the query cache #2667
Labels
Comments
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Still an issue. I don't know exactly what the caching is doing, but I mainly wanted to enable it to reduce disk writes because I have many entities which are updating like all two seconds. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the issue you are experiencing
I noticed that the mariadb addon has the query cache turned off by default. Turning it on via
query_cache_type=on
andquery_cache_size=2097152
gave me a significant performance improvement on my Rasberry Pi 4 when (re)loading graphs with many values.It would be neat if the query cache size could be set via the settings options of the add-on and have a sensible default, like 10% memory of the host? :)
What type of installation are you running?
Home Assistant OS
Which operating system are you running on?
Home Assistant Operating System
Which add-on are you reporting an issue with?
MariaDB
What is the version of the add-on?
2.5.1
Steps to reproduce the issue
query_cache_size
andquery_cache_type
which are zero and 'OFF'Anything in the Supervisor logs that might be useful for us?
No response
Anything in the add-on logs that might be useful for us?
No response
Additional information
Documentation on these options:
https://mariadb.com/kb/en/server-system-variables/#query_cache_type
https://mariadb.com/kb/en/server-system-variables/#query_cache_size
The text was updated successfully, but these errors were encountered: