mariaDB cache 설정
2019.08.04 16:59
https://easyengine.io/tutorials/mysql/query-cache/
안하면 엄청 느리다.
Important Note: From MySQL 5.6.8,query_cache_type
is set to OFF by default. So if you haven’t explicitly turned it ON on old version, it may not work anymore!
Check current status of query_cache
mysql -e "show variables like 'query_cache_%'"
Will output something like:
+------------------------------+-----------+ | Variable_name | Value | +------------------------------+-----------+ | query_cache_limit | 2097152 | | query_cache_min_res_unit | 4096 | | query_cache_size | 268435456 | | query_cache_strip_comments | ON | | query_cache_type | ON | | query_cache_wlock_invalidate | OFF | +------------------------------+-----------+
Query Cache Config
Add something like below following to your /etc/my/my.cnf
query_cache_type = 1 query_cache_size = 256M query_cache_limit = 2M query_cache_strip_comments =1
Please note that query_cache_strip_comments
variable is available on Percona & MariaDB mysql variants as of now.
Meaning of variables
query_cache_type
Just turn it ON. From mysql 5.6.8 its OFF by default.
If this is OFF, you will see error “[!!] Query cache is disabled” when running mysqltuner.
Earlier mysql version used to setquery_cache_type
= 1 butquery_cache_size
= 0. If either ofquery_cache_type
andquery_cache_size
is set to 0, query_cache gets disabled.
query_cache_size
Default is 1MB. You can set it upto 4GB but very high values are not recommend for sites where tables are modified quite frequently.
In WordPress scenario, if you have a multi-author blog, or some other custom post types, then query cache prunes might be frequent. Query cache is invalidated for entire table even if a small value is modified.
query_cache_limit
Default is 1MB. You can set it upto 4GB. Again very high values are not recommended.
Better optimize your codes to not fetch too much data in one query. If you need 10 rows, add pagination, WHERE conditions rather than fetching all rows from mysql and then using only 10 rows out of them!
InnoDB Buffer & Query Cache
Many references on Internet will tell you that query cache is useless if InnoDB is being used.
Well if you are using InnoDB only and have limited RAM, InnoDB buffer pool without a doubt should get first priority.
If you have some spare RAM, it is highly recommended to use query_cache for WordPress sites. Even for big WordPress sites, most likely percentage of SELECT queries will be much higher as compared to INSERT or UPDATE.
Best way is to monitor query cache efficiency using mysqltuner. Look for a line like:
[OK] Query cache efficiency: 71.5% (8K cached / 11K selects)
100% Query cache efficiency may not be possible for 100% read-only sites but try to stay above 50%.
댓글 0
번호 | 제목 | 글쓴이 | 날짜 | 조회 수 |
---|---|---|---|---|
1641 | 이사 감사 3년 변경등기 | WHRIA | 2015.12.02 | 56 |
1640 | sqlite to mysql | WHRIA | 2016.10.18 | 57 |
1639 | lvm 축소 확장 [4] | WHRIA | 2020.01.13 | 57 |
1638 | php 세션 로그인 | WHRIA | 2020.04.24 | 57 |
1637 | bay trail ubuntu 20.04 [1] | WHRIA | 2020.12.24 | 57 |
1636 | 저녁 10시에 자동 종료 스크립트 | WHRIA | 2016.06.25 | 59 |
1635 | swap memory | WHRIA | 2019.03.14 | 59 |
1634 | 정량화 논문들 | WHRIA | 2023.02.16 | 60 |
1633 | sroc [1] | WHRIA | 2020.12.10 | 61 |
1632 | zmq async client server [1] | WHRIA | 2020.03.12 | 62 |
1631 | chat GPT | WHRIA | 2023.02.16 | 62 |
1630 | LG 글로벌 | WHRIA | 2019.01.31 | 63 |
1629 | 원격 진료 | WHRIA | 2023.03.23 | 63 |
1628 | 드리블 | WHRIA | 2019.04.12 | 64 |
1627 | xml json pascal [4] | WHRIA | 2020.01.12 | 64 |