Configuring caching in MySQL

Configuring caching in MySQL can significantly enhance database performance by reducing query execution times. Below are the steps to configure caching in MySQL:


1. Enable Query Cache

The query cache is used to store the results of SELECT queries. If the same query is executed again, MySQL can return the cached result without re-executing the query.

Steps:
  1. Check if the query cache is enabled:

    SHOW VARIABLES LIKE 'query_cache%';

  2. Enable and configure query cache in the MySQL configuration file (my.cnf or my.ini):

    [mysqld] query_cache_type = 1 # 1 = ON, 2 = DEMAND (only cache queries with SQL_CACHE) query_cache_size = 128M # Set the size of the query cache query_cache_limit = 2M # Maximum size of individual query results to cache

  3. Restart the MySQL service to apply changes:

    sudo service mysql restart

  4. Use SQL_CACHE or SQL_NO_CACHE in queries (if query_cache_type = 2):

    SELECT SQL_CACHE * FROM my_table WHERE id = 1;


2. Use InnoDB Buffer Pool

For the InnoDB storage engine, the InnoDB Buffer Pool is the primary caching mechanism for data and indexes.

Steps:
  1. Configure the buffer pool size in my.cnf:

    [mysqld] innodb_buffer_pool_size = 4G # Set it to about 70-80% of total available memory innodb_buffer_pool_instances = 4 # Number of buffer pool instances (for large buffer sizes)

  2. Restart MySQL:

    sudo service mysql restart

  3. Monitor usage:

    SHOW ENGINE INNODB STATUS\G;


3. Configure Table Cache

The table cache determines how many table handles MySQL can keep open at a time.

Steps:
  1. Configure table_open_cache in my.cnf:

    [mysqld] table_open_cache = 2000 # Adjust based on workload

  2. Monitor open tables:

    SHOW STATUS LIKE 'Open_tables';


4. Use Performance Schema and Query Optimization

MySQL includes a Performance Schema to monitor and optimize queries, which helps identify which queries to cache or optimize.

Steps:
  1. Enable Performance Schema:

    [mysqld] performance_schema = ON

  2. Analyze slow queries:

    SHOW FULL PROCESSLIST;

  3. Enable and configure the slow query log:

    [mysqld] slow_query_log = 1 slow_query_log_file = /var/log/mysql-slow.log long_query_time = 1

  4. Restart MySQL and review slow queries:

    sudo service mysql restart tail -f /var/log/mysql-slow.log


5. Use Proxy Cache (Optional)

Consider using a proxy tool like ProxySQL for advanced query caching mechanisms.


6. Monitor Cache Usage

Use these commands to monitor caching performance:

  • Query cache: SHOW STATUS LIKE 'Qcache%';

  • InnoDB buffer pool: SHOW STATUS LIKE 'Innodb_buffer_pool%';

相关推荐
NineData2 分钟前
NineData 迁移评估功能正式上线
数据库·dba
NineData5 小时前
数据库迁移总踩坑?用 NineData 迁移评估,提前识别所有兼容性风险
数据库·程序员·云计算
赵渝强老师8 小时前
【赵渝强老师】PostgreSQL中表的碎片
数据库·postgresql
全栈老石12 小时前
拆解低代码引擎核心:元数据驱动的"万能表"架构
数据库·低代码
倔强的石头_1 天前
kingbase备份与恢复实战(二)—— sys_dump库级逻辑备份与恢复(Windows详细步骤)
数据库
jiayou642 天前
KingbaseES 实战:深度解析数据库对象访问权限管理
数据库
于眠牧北3 天前
MySQL的锁类型,表锁,行锁,MVCC中所使用的临键锁
mysql
李广坤3 天前
MySQL 大表字段变更实践(改名 + 改类型 + 改长度)
数据库
Turnip12024 天前
深度解析:为什么简单的数据库"写操作"会在 MySQL 中卡住?
后端·mysql
爱可生开源社区4 天前
2026 年,优秀的 DBA 需要具备哪些素质?
数据库·人工智能·dba