通过show variables like xxx 详解mysql运行时参数 本文参考以下网页: 1.http://dev.mysql.com/doc/refman/5.1/en/server-status-variables.htm 2.http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html 3.http://www.ibm.com/developerwork
通过show variables like xxx 详解mysql运行时参数本文参考以下网页:
1.http://dev.mysql.com/doc/refman/5.1/en/server-status-variables.htm
2.http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html
3.http://www.ibm.com/developerworks/cn/linux/l-tune-lamp-3.html
4.http://www.day32.com/MySQL/tuning-primer.sh 具体数值主要参考此工具
?
1, 查看MySQL服务器配置信息?
Java代码??
- mysql>?show?variables;??
2, 查看MySQL服务器运行的各种状态值?

- mysql>?show?global?status;??
3, 慢查询?

- mysql>?show?variables?like?'%slow%';??
- +------------------+-------+??
- |?Variable_name????|?Value?|??
- +------------------+-------+??
- |?log_slow_queries?|?OFF???|??
- |?slow_launch_time?|?2?????|??
- +------------------+-------+??
- mysql>?show?global?status?like?'%slow%';??
- +---------------------+-------+??
- |?Variable_name???????|?Value?|??
- +---------------------+-------+??
- |?Slow_launch_threads?|?0?????|??
- |?Slow_queries????????|?279???|??
- +---------------------+-------+??
配置中关闭了记录慢查询(最好是打开,方便优化),超过2秒即为慢查询,一共有279条慢查询?
4, 连接数?

- mysql>?show?variables?like?'max_connections';??
- +-----------------+-------+??
- |?Variable_name???|?Value?|??
- +-----------------+-------+??
- |?max_connections?|?500???|??
- +-----------------+-------+??
- ??
- mysql>?show?global?status?like?'max_used_connections';??
- +----------------------+-------+??
- |?Variable_name????????|?Value?|??
- +----------------------+-------+??
- |?Max_used_connections?|?498???|??
- +----------------------+-------+??
设置的最大连接数是500,而响应的连接数是498?
max_used_connections / max_connections * 100% = 99.6% (理想值 ≈ 85%)?
5, key_buffer_size?
key_buffer_size是对MyISAM表性能影响最大的一个参数, 不过数据库中多为Innodb?

- mysql>?show?variables?like?'key_buffer_size';??
- +-----------------+----------+??
- |?Variable_name???|?Value????|??
- +-----------------+----------+??
- |?key_buffer_size?|?67108864?|??
- +-----------------+----------+??
- ??
- mysql>?show?global?status?like?'key_read%';??
- +-------------------+----------+??
- |?Variable_name?????|?Value????|??
- +-------------------+----------+??
- |?Key_read_requests?|?25629497?|??
- |?Key_reads?????????|?66071????|??
- +-------------------+----------+??
一共有25629497个索引读取请求,有66071个请求在内存中没有找到直接从硬盘读取索引,计算索引未命中缓存的概率:?
key_cache_miss_rate = Key_reads / Key_read_requests * 100% =0.27%?
需要适当加大key_buffer_size?

- mysql>?show?global?status?like?'key_blocks_u%';??
- +-------------------+-------+??
- |?Variable_name?????|?Value?|??
- +-------------------+-------+??
- |?Key_blocks_unused?|?10285?|??
- |?Key_blocks_used???|?47705?|??
- +-------------------+-------+??
Key_blocks_unused表示未使用的缓存簇(blocks)数,Key_blocks_used表示曾经用到的最大的blocks数?
Key_blocks_used / (Key_blocks_unused + Key_blocks_used) * 100% ≈ 18% (理想值 ≈ 80%)?
6, 临时表?

- mysql>?show?global?status?like?'created_tmp%';??
- +-------------------------+---------+??
- |?Variable_name???????????|?Value???|??
- +-------------------------+---------+??
- |?Created_tmp_disk_tables?|?4184337?|??
- |?Created_tmp_files???????|?4124????|??
- |?Created_tmp_tables??????|?4215028?|??
- +-------------------------+---------+??
每次创建临时表,Created_tmp_tables增加,如果是在磁盘上创建临时表,Created_tmp_disk_tables也增加,Created_tmp_files表示MySQL服务创建的临时文件文件数:?
Created_tmp_disk_tables / Created_tmp_tables * 100% = 99% (理想值

- mysql>?show?variables?where?Variable_name?in?('tmp_table_size',?'max_heap_table_size');??
- +---------------------+-----------+??
- |?Variable_name???????|?Value?????|??
- +---------------------+-----------+??
- |?max_heap_table_size?|?134217728?|??
- |?tmp_table_size??????|?134217728?|??
- +---------------------+-----------+??
需要增加tmp_table_size?
7,open table 的情况?

- mysql>?show?global?status?like?'open%tables%';??
- +---------------+-------+??
- |?Variable_name?|?Value?|??
- +---------------+-------+??
- |?Open_tables???|?1024??|??
- |?Opened_tables?|?1465??|??
- +---------------+-------+??
Open_tables 表示打开表的数量,Opened_tables表示打开过的表数量,如果Opened_tables数量过大,说明配置中 table_cache(5.1.3之后这个值叫做table_open_cache)值可能太小,我们查询一下服务器table_cache值?

- mysql>?show?variables?like?'table_cache';??
- +---------------+-------+??
- |?Variable_name?|?Value?|??
- +---------------+-------+??
- |?table_cache???|?1024??|??
- +---------------+-------+??
Open_tables / Opened_tables * 100% =69% 理想值 (>= 85%)?
Open_tables / table_cache * 100% = 100% 理想值 (
8, 进程使用情况?

- mysql>?show?global?status?like?'Thread%';??
- +-------------------+-------+??
- |?Variable_name?????|?Value?|??
- +-------------------+-------+??
- |?Threads_cached????|?31????|??
- |?Threads_connected?|?239???|??
- |?Threads_created???|?2914??|??
- |?Threads_running???|?4?????|??
- +-------------------+-------+??
如果我们在MySQL服务器配置文件中设置了thread_cache_size,当客户端断开之后,服务器处理此客户的线程将会缓存起来以响应下一个客户而不是销毁(前提是缓存数未达上限)。Threads_created表示创建过的线程数,如果发现Threads_created值过大的话,表明 MySQL服务器一直在创建线程,这也是比较耗资源,可以适当增加配置文件中thread_cache_size值,查询服务器 thread_cache_size配置:?

- mysql>?show?variables?like?'thread_cache_size';??
- +-------------------+-------+??
- |?Variable_name?????|?Value?|??
- +-------------------+-------+??
- |?thread_cache_size?|?32????|??
- +-------------------+-------+??
9, 查询缓存(query cache)?

- mysql>?show?global?status?like?'qcache%';??
- +-------------------------+----------+??
- |?Variable_name???????????|?Value????|??
- +-------------------------+----------+??
- |?Qcache_free_blocks??????|?2226?????|??
- |?Qcache_free_memory??????|?10794944?|??
- |?Qcache_hits?????????????|?5385458??|??
- |?Qcache_inserts??????????|?1806301??|??
- |?Qcache_lowmem_prunes????|?433101???|??
- |?Qcache_not_cached???????|?4429464??|??
- |?Qcache_queries_in_cache?|?7168?????|??
- |?Qcache_total_blocks?????|?16820????|??
- +-------------------------+----------+??
Qcache_free_blocks:缓存中相邻内存块的个数。数目大说明可能有碎片。FLUSH QUERY CACHE会对缓存中的碎片进行整理,从而得到一个空闲块。?
Qcache_free_memory:缓存中的空闲内存。?
Qcache_hits:每次查询在缓存中命中时就增大?
Qcache_inserts:每次插入一个查询时就增大。命中次数除以插入次数就是不中比率。?
Qcache_lowmem_prunes:缓存出现内存不足并且必须要进行清理以便为更多查询提供空间的次数。这个数字最好长时间来看;如果这个数字在不断增长,就表示可能碎片非常严重,或者内存很少。(上面的????????? free_blocks和free_memory可以告诉您属于哪种情况)?
Qcache_not_cached:不适合进行缓存的查询的数量,通常是由于这些查询不是 SELECT 语句或者用了now()之类的函数。?
Qcache_queries_in_cache:当前缓存的查询(和响应)的数量。?
Qcache_total_blocks:缓存中块的数量。?
我们再查询一下服务器关于query_cache的配置:?

- mysql>?show?variables?like?'query_cache%';??
- +------------------------------+----------+??
- |?Variable_name????????????????|?Value????|??
- +------------------------------+----------+??
- |?query_cache_limit????????????|?33554432?|??
- |?query_cache_min_res_unit?????|?4096?????|??
- |?query_cache_size?????????????|?33554432?|??
- |?query_cache_type?????????????|?ON???????|??
- |?query_cache_wlock_invalidate?|?OFF??????|??
- +------------------------------+----------+??
各字段的解释:?
query_cache_limit:超过此大小的查询将不缓存?
query_cache_min_res_unit:缓存块的最小大小?
query_cache_size:查询缓存大小?
query_cache_type:缓存类型,决定缓存什么样的查询,示例中表示不缓存 select sql_no_cache 查询?
query_cache_wlock_invalidate:当有其他客户端正在对MyISAM表进行写操作时,如果查询在query cache中,是否返回cache结果还是等写操作完成再读表获取结果。?
query_cache_min_res_unit的配置是一柄”双刃剑”,默认是4KB,设置值大对大数据查询有好处,但如果你的查询都是小数据查询,就容易造成内存碎片和浪费。?
查询缓存碎片率 = Qcache_free_blocks / Qcache_total_blocks * 100%?
如果查询缓存碎片率超过20%,可以用FLUSH QUERY CACHE整理缓存碎片,或者试试减小query_cache_min_res_unit,如果你的查询都是小数据量的话。?
查询缓存利用率 = (query_cache_size – Qcache_free_memory) / query_cache_size * 100%?
查询缓存利用率在25%以下的话说明query_cache_size设置的过大,可适当减小;查询缓存利用率在80%以上而且Qcache_lowmem_prunes > 50的话说明query_cache_size可能有点小,要不就是碎片太多。?
查询缓存命中率 = (Qcache_hits – Qcache_inserts) / Qcache_hits * 100%?
示例服务器 查询缓存碎片率 = 20.46%,查询缓存利用率 = 62.26%,查询缓存命中率 = 1.94%,命中率很差,可能写操作比较频繁吧,而且可能有些碎片。?
10,排序使用情况?

- mysql>?show?global?status?like?'sort%';??
- +-------------------+----------+??
- |?Variable_name?????|?Value????|??
- +-------------------+----------+??
- |?Sort_merge_passes?|?2136?????|??
- |?Sort_range????????|?81888????|??
- |?Sort_rows?????????|?35918141?|??
- |?Sort_scan?????????|?55269????|??
- +-------------------+----------+??
Sort_merge_passes 包括两步。MySQL 首先会尝试在内存中做排序,使用的内存大小由系统变量 Sort_buffer_size 决定,如果它的大小不够把所有的记录都读到内存中,MySQL 就会把每次在内存中排序的结果存到临时文件中,等 MySQL 找到所有记录之后,再把临时文件中的记录做一次排序。这再次排序就会增加 Sort_merge_passes。实际上,MySQL 会用另一个临时文件来存再次排序的结果,所以通常会看到 Sort_merge_passes 增加的数值是建临时文件数的两倍。因为用到了临时文件,所以速度可能会比较慢,增加 Sort_buffer_size 会减少 Sort_merge_passes 和 创建临时文件的次数。但盲目的增加 Sort_buffer_size 并不一定能提高速度,见 How fast can you sort data with MySQL?(引自http://qroom.blogspot.com/2007/09/mysql-select-sort.html)?
另外,增加read_rnd_buffer_size(3.2.3是record_rnd_buffer_size)的值对排序的操作也有一点的好处,参见:http://www.mysqlperformanceblog.com/2007/07/24/what-exactly-is- read_rnd_buffer_size/?
11.文件打开数(open_files)?

- mysql>?show?global?status?like?'open_files';??
- +---------------+-------+??
- |?Variable_name?|?Value?|??
- +---------------+-------+??
- |?Open_files????|?821???|??
- +---------------+-------+??
- ??
- mysql>?show?variables?like?'open_files_limit';??
- +------------------+-------+??
- |?Variable_name????|?Value?|??
- +------------------+-------+??
- |?open_files_limit?|?65535?|??
- +------------------+-------+??
比较合适的设置:Open_files / open_files_limit * 100%
正常?
12。 表锁情况?

- mysql>?show?global?status?like?'table_locks%';??
- +-----------------------+---------+??
- |?Variable_name?????????|?Value???|??
- +-----------------------+---------+??
- |?Table_locks_immediate?|?4257944?|??
- |?Table_locks_waited????|?25182???|??
- +-----------------------+---------+??
Table_locks_immediate 表示立即释放表锁数,Table_locks_waited表示需要等待的表锁数,如果 Table_locks_immediate / Table_locks_waited > 5000,最好采用InnoDB引擎,因为InnoDB是行锁而MyISAM是表锁,对于高并发写入的应用InnoDB效果会好些.?
13. 表扫描情况?

- mysql>?show?global?status?like?'handler_read%';??
- +-----------------------+-----------+??
- |?Variable_name?????????|?Value?????|??
- +-----------------------+-----------+??
- |?Handler_read_first????|?108763????|??
- |?Handler_read_key??????|?92813521??|??
- |?Handler_read_next?????|?486650793?|??
- |?Handler_read_prev?????|?688726????|??
- |?Handler_read_rnd??????|?9321362???|??
- |?Handler_read_rnd_next?|?153086384?|??
- +-----------------------+-----------+??
各字段解释参见http://hi.baidu.com/thinkinginlamp/blog/item/31690cd7c4bc5cdaa144df9c.html,调出服务器完成的查询请求次数:?

- mysql>?show?global?status?like?'com_select';??
- +---------------+---------+??
- |?Variable_name?|?Value???|??
- +---------------+---------+??
- |?Com_select????|?2693147?|??
- +---------------+---------+??
计算表扫描率:?
表扫描率 = Handler_read_rnd_next / Com_select?
如果表扫描率超过4000,说明进行了太多表扫描,很有可能索引没有建好,增加read_buffer_size值会有一些好处,但最好不要超过8MB。
----------------------------------------------

MySQL is an open source relational database management system, mainly used to store and retrieve data quickly and reliably. Its working principle includes client requests, query resolution, execution of queries and return results. Examples of usage include creating tables, inserting and querying data, and advanced features such as JOIN operations. Common errors involve SQL syntax, data types, and permissions, and optimization suggestions include the use of indexes, optimized queries, and partitioning of tables.

MySQL is an open source relational database management system suitable for data storage, management, query and security. 1. It supports a variety of operating systems and is widely used in Web applications and other fields. 2. Through the client-server architecture and different storage engines, MySQL processes data efficiently. 3. Basic usage includes creating databases and tables, inserting, querying and updating data. 4. Advanced usage involves complex queries and stored procedures. 5. Common errors can be debugged through the EXPLAIN statement. 6. Performance optimization includes the rational use of indexes and optimized query statements.

MySQL is chosen for its performance, reliability, ease of use, and community support. 1.MySQL provides efficient data storage and retrieval functions, supporting multiple data types and advanced query operations. 2. Adopt client-server architecture and multiple storage engines to support transaction and query optimization. 3. Easy to use, supports a variety of operating systems and programming languages. 4. Have strong community support and provide rich resources and solutions.

InnoDB's lock mechanisms include shared locks, exclusive locks, intention locks, record locks, gap locks and next key locks. 1. Shared lock allows transactions to read data without preventing other transactions from reading. 2. Exclusive lock prevents other transactions from reading and modifying data. 3. Intention lock optimizes lock efficiency. 4. Record lock lock index record. 5. Gap lock locks index recording gap. 6. The next key lock is a combination of record lock and gap lock to ensure data consistency.

The main reasons for poor MySQL query performance include not using indexes, wrong execution plan selection by the query optimizer, unreasonable table design, excessive data volume and lock competition. 1. No index causes slow querying, and adding indexes can significantly improve performance. 2. Use the EXPLAIN command to analyze the query plan and find out the optimizer error. 3. Reconstructing the table structure and optimizing JOIN conditions can improve table design problems. 4. When the data volume is large, partitioning and table division strategies are adopted. 5. In a high concurrency environment, optimizing transactions and locking strategies can reduce lock competition.

In database optimization, indexing strategies should be selected according to query requirements: 1. When the query involves multiple columns and the order of conditions is fixed, use composite indexes; 2. When the query involves multiple columns but the order of conditions is not fixed, use multiple single-column indexes. Composite indexes are suitable for optimizing multi-column queries, while single-column indexes are suitable for single-column queries.

To optimize MySQL slow query, slowquerylog and performance_schema need to be used: 1. Enable slowquerylog and set thresholds to record slow query; 2. Use performance_schema to analyze query execution details, find out performance bottlenecks and optimize.

MySQL and SQL are essential skills for developers. 1.MySQL is an open source relational database management system, and SQL is the standard language used to manage and operate databases. 2.MySQL supports multiple storage engines through efficient data storage and retrieval functions, and SQL completes complex data operations through simple statements. 3. Examples of usage include basic queries and advanced queries, such as filtering and sorting by condition. 4. Common errors include syntax errors and performance issues, which can be optimized by checking SQL statements and using EXPLAIN commands. 5. Performance optimization techniques include using indexes, avoiding full table scanning, optimizing JOIN operations and improving code readability.


Hot AI Tools

Undresser.AI Undress
AI-powered app for creating realistic nude photos

AI Clothes Remover
Online AI tool for removing clothes from photos.

Undress AI Tool
Undress images for free

Clothoff.io
AI clothes remover

AI Hentai Generator
Generate AI Hentai for free.

Hot Article

Hot Tools

SublimeText3 Mac version
God-level code editing software (SublimeText3)

DVWA
Damn Vulnerable Web App (DVWA) is a PHP/MySQL web application that is very vulnerable. Its main goals are to be an aid for security professionals to test their skills and tools in a legal environment, to help web developers better understand the process of securing web applications, and to help teachers/students teach/learn in a classroom environment Web application security. The goal of DVWA is to practice some of the most common web vulnerabilities through a simple and straightforward interface, with varying degrees of difficulty. Please note that this software

SublimeText3 Chinese version
Chinese version, very easy to use

mPDF
mPDF is a PHP library that can generate PDF files from UTF-8 encoded HTML. The original author, Ian Back, wrote mPDF to output PDF files "on the fly" from his website and handle different languages. It is slower than original scripts like HTML2FPDF and produces larger files when using Unicode fonts, but supports CSS styles etc. and has a lot of enhancements. Supports almost all languages, including RTL (Arabic and Hebrew) and CJK (Chinese, Japanese and Korean). Supports nested block-level elements (such as P, DIV),

EditPlus Chinese cracked version
Small size, syntax highlighting, does not support code prompt function