下载地址:https://launchpad.net/mysql-tuning-primer
将tuning-primer.sh 放在mysql所在的server,
若出现如下错误
[root@hbase1 ~]# sh tuning-primer.sh all which: no bc in (/usr/local/sbin:/usr/local/bin:/sbin:/bin:/usr/sbin:/usr/bin:/usr/local/jdk1.6.0_31/bin:/usr/local/apache-ant-1.8.3/bin:/root/bin) Error: Command line calculator 'bc' not found!
请安装bc,
[root@hbase1 ~]# yum install bc
再次运行,生成报告:
-- MYSQL PERFORMANCE TUNING PRIMER -- - By: Matthew Montgomery - MySQL Version 5.1.67 x86_64 Uptime = 55 days 22 hrs 20 min 50 sec Avg. qps = 48 Total Questions = 234566845 Threads Connected = 205 Server has been running for over 48hrs. It should be safe to follow these recommendations To find out more information on how each of these runtime variables effects performance visit: http://dev.mysql.com/doc/refman/5.1/en/server-system-variables.html Visit http://www.mysql.com/products/enterprise/advisors.html for info about MySQL's Enterprise Monitoring and Advisory Service SLOW QUERIES The slow query log is NOT enabled. Current long_query_time = 10.000000 sec. You have 1345 out of 234566882 that take longer than 10.000000 sec. to complete Your long_query_time seems to be fine BINARY UPDATE LOG The binary update log is NOT enabled. You will not be able to do point in time recovery See http://dev.mysql.com/doc/refman/5.1/en/point-in-time-recovery.html WORKER THREADS Current thread_cache_size = 8 Current threads_cached = 5 Current threads_per_sec = 0 Historic threads_per_sec = 0 Your thread_cache_size is fine MAX CONNECTIONS Current max_connections = 1000 Current threads_connected = 205 Historic max_used_connections = 410 The number of used connections is 41% of the configured maximum. Your max_connections variable seems to be fine. INNODB STATUS Current InnoDB index space = 3.64 G Current InnoDB data space = 17.16 G Current InnoDB buffer pool free = 0 % Current innodb_buffer_pool_size = 8 M Depending on how much space your innodb indexes take up it may be safe to increase this value to up to 2 / 3 of total system memory MEMORY USAGE Max Memory Ever Allocated : 1.11 G Configured Max Per-thread Buffers : 2.68 G Configured Max Global Buffers : 17 M Configured Max Memory Limit : 2.70 G Physical Memory : 7.67 G Max memory limit seem to be within acceptable norms KEY BUFFER Current MyISAM index space = 1.28 G Current key_buffer_size = 7 M Key cache miss rate is 1 : 814 Key buffer free ratio = 81 % Your key_buffer_size seems to be fine QUERY CACHE Query cache is supported but not enabled Perhaps you should set the query_cache_size SORT OPERATIONS Current sort_buffer_size = 2 M Current read_rnd_buffer_size = 256 K Sort buffer seems to be fine JOINS Current join_buffer_size = 132.00 K You have had 62754 queries where a join could not use an index properly You should enable "log-queries-not-using-indexes" Then look for non indexed joins in the slow query log. If you are unable to optimize your queries you may want to increase your join_buffer_size to accommodate larger joins in one pass. Note! This script will still suggest raising the join_buffer_size when ANY joins not using indexes are found. OPEN FILES LIMIT Current open_files_limit = 65535 files The open_files_limit should typically be set to at least 2x-3x that of table_cache if you have heavy MyISAM usage. Your open_files_limit value seems to be fine TABLE CACHE Current table_open_cache = 1024 tables Current table_definition_cache = 256 tables You have a total of 6130 tables You have 1024 open tables. Current table_cache hit rate is 0% , while 100% of your table cache is in use You should probably increase your table_cache You should probably increase your table_definition_cache value. TEMP TABLES Current max_heap_table_size = 16 M Current tmp_table_size = 16 M Of 12719708 temp tables, 1% were created on disk Created disk tmp tables ratio seems fine TABLE SCANS Current read_buffer_size = 128 K Current table scan ratio = 836 : 1 read_buffer_size seems to be fine TABLE LOCKING Current Lock Wait ratio = 1 : 1605886 Your table locking seems to be fine
根据上面提到的指标慢慢优化。