tuning-primer.sh mysql 報表

標籤：

[[email protected] mytop-1.6]# wget http://www.day32.com/MySQL/tuning-primer.sh     --2016-07-03 19:42:33--  http://www.day32.com/MySQL/tuning-primer.shResolving www.day32.com... 192.237.221.190Connecting to www.day32.com|192.237.221.190|:80... connected.HTTP request sent, awaiting response... 200 OKLength: 51892 (51K) [application/x-sh]Saving to: “tuning-primer.sh”100%[=========================================================================>] 51,892       109K/s   in 0.5s    2016-07-03 19:42:34 (109 KB/s) - “tuning-primer.sh” saved [51892/51892][[email protected] mytop-1.6]# chmod +x tuning-primer.sh [[email protected] mytop-1.6]# ./tuning-primer.sh Using login values from ~/.my.cnf- INITIAL LOGIN ATTEMPT FAILED -Testing for stored webmin passwords: None FoundCould not auto detect login info!Found potential sockets: /tmp/mysql.sock5Using: /tmp/mysql.sock5Would you like to provide a different socket?: [y/N] ySocket: /tmp/mysql.sock5Do you have your login handy ? [y/N] : yUser: rootPassword: Aa@12345 Would you like me to create a ~/.my.cnf file for you? [y/N] : n         -- MYSQL PERFORMANCE TUNING PRIMER --             - By: Matthew Montgomery -MySQL Version 5.6.27 x86_64Uptime = 0 days 2 hrs 48 min 22 secAvg. qps = 0Total Questions = 892Threads Connected = 3Warning: Server has not been running for at least 48hrs.It may not be safe to use these recommendationsTo find out more information on how each of theseruntime variables effects performance visit:http://dev.mysql.com/doc/refman/5.6/en/server-system-variables.htmlVisit http://www.mysql.com/products/enterprise/advisors.htmlfor info about MySQL‘s Enterprise Monitoring and Advisory ServiceSLOW QUERIESThe slow query log is NOT enabled.Current long_query_time = 10.000000 sec.You have 0 out of 913 that take longer than 10.000000 sec. to completeYour long_query_time seems to be fineBINARY UPDATE LOGThe binary update log is NOT enabled.You will not be able to do point in time recoverySee http://dev.mysql.com/doc/refman/5.6/en/point-in-time-recovery.htmlWORKER THREADSCurrent thread_cache_size = 9Current threads_cached = 0Current threads_per_sec = 0Historic threads_per_sec = 0Your thread_cache_size is fineMAX CONNECTIONSCurrent max_connections = 151Current threads_connected = 3Historic max_used_connections = 3The number of used connections is 1% of the configured maximum.You are using less than 10% of your configured max_connections.Lowering max_connections could help to avoid an over-allocation of memorySee "MEMORY USAGE" section to make sure you are not over-allocatingINNODB STATUSCurrent InnoDB index space = 1.47 GCurrent InnoDB data space = 1.28 GCurrent InnoDB buffer pool free = 77 %Current innodb_buffer_pool_size = 32 MDepending on how much space your innodb indexes take up it may be safeto increase this value to up to 2 / 3 of total system memoryMEMORY USAGEMax Memory Ever Allocated : 60 MConfigured Max Per-thread Buffers : 169 MConfigured Max Global Buffers : 57 MConfigured Max Memory Limit : 226 MPhysical Memory : 1.30 GMax memory limit seem to be within acceptable normsKEY BUFFERCurrent MyISAM index space = 118 KCurrent key_buffer_size = 8 MKey cache miss rate is 1 : 16Key buffer free ratio = 81 %Your key_buffer_size seems to be fineQUERY CACHEQuery cache is enabledCurrent query_cache_size = 1 MCurrent query_cache_used = 16 KCurrent query_cache_limit = 1 MCurrent Query cache Memory fill ratio = 1.64 %Current query_cache_min_res_unit = 4 KYour query_cache_size seems to be too high.Perhaps you can use these resources elsewhereMySQL won‘t cache query results that are larger than query_cache_limit in sizeSORT OPERATIONSCurrent sort_buffer_size = 256 KCurrent read_rnd_buffer_size = 256 KNo sort operations have been performedSort buffer seems to be fineJOINSCurrent join_buffer_size = 260.00 KYou have had 0 queries where a join could not use an index properlyYour joins seem to be using indexes properlyOPEN FILES LIMITCurrent open_files_limit = 5000 filesThe open_files_limit should typically be set to at least 2x-3xthat of table_cache if you have heavy MyISAM usage.Your open_files_limit value seems to be fineTABLE CACHECurrent table_open_cache = 2000 tablesCurrent table_definition_cache = 1400 tablesYou have a total of 113 tablesYou have 117 open tables.The table_cache value seems to be fineTEMP TABLESCurrent max_heap_table_size = 16 MCurrent tmp_table_size = 16 MOf 1072 temp tables, 6% were created on diskCreated disk tmp tables ratio seems fineTABLE SCANSCurrent read_buffer_size = 128 KCurrent table scan ratio = 440 : 1read_buffer_size seems to be fineTABLE LOCKINGCurrent Lock Wait ratio = 0 : 1168Your table locking seems to be fine

 

tuning-primer.sh mysql 報表