Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- -- MYSQL PERFORMANCE TUNING PRIMER --
- - By: Matthew Montgomery -
- MySQL Version 10.0.21-MariaDB-log amd64
- Uptime = 4 days 23 hrs 18 min 0 sec
- Avg. qps = 12
- Total Questions = 5275601
- Threads Connected = 3
- 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/10.0/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 0 out of 5275622 that take longer than 10.000000 sec. to complete
- [: 0.00000000000000000000: bad number
- Your long_query_time seems to be fine
- BINARY UPDATE LOG
- The binary update log is enabled
- Binlog sync is not enabled, you could loose binlog records during a server crash
- WORKER THREADS
- Current thread_cache_size = 8
- Current threads_cached = 6
- Current threads_per_sec = 0
- Historic threads_per_sec = 0
- Your thread_cache_size is fine
- MAX CONNECTIONS
- Current max_connections = 250
- Current threads_connected = 3
- Historic max_used_connections = 10
- The number of used connections is 4% 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 memory
- See "MEMORY USAGE" section to make sure you are not over-allocating
- INNODB STATUS
- Current InnoDB index space = 384 K
- Current InnoDB data space = 608 K
- Current InnoDB buffer pool free = 99 %
- Current innodb_buffer_pool_size = 3.00 G
- 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 : 3.57 G
- Configured Max Per-thread Buffers : 3.73 G
- Configured Max Global Buffers : 3.42 G
- Configured Max Memory Limit : 7.16 G
- Physical Memory : 8.00 G
- Max memory limit seem to be within acceptable norms
- KEY BUFFER
- Current MyISAM index space = 0 bytes
- Current key_buffer_size = 384 M
- Key cache miss rate is 1 : 7261
- Key buffer free ratio = 79 %
- Your key_buffer_size seems to be fine
- QUERY CACHE
- Query cache is enabled
- Current query_cache_size = 32 M
- Current query_cache_used = 17 M
- Current query_cache_limit = 512 K
- Current Query cache Memory fill ratio = 54.57 %
- Current query_cache_min_res_unit = 4 K
- Query Cache is 27 % fragmented
- Run "FLUSH QUERY CACHE" periodically to defragment the query cache memory
- If you have many small queries lower 'query_cache_min_res_unit' to reduce fragmentation.
- MySQL won't cache query results that are larger than query_cache_limit in size
- SORT OPERATIONS
- Current sort_buffer_size = 4 M
- Current read_rnd_buffer_size = 8 M
- Sort buffer seems to be fine
- JOINS
- Current join_buffer_size = 1.00 M
- You have had 67 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 = 235233 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 = 1536 tables
- Current table_definition_cache = 768 tables
- You have a total of 11 tables
- You have 427 open tables.
- The table_cache value seems to be fine
- TEMP TABLES
- Current max_heap_table_size = 1.00 G
- Current tmp_table_size = 1.00 G
- Of 54408 temp tables, 50% were created on disk
- Perhaps you should increase your tmp_table_size and/or max_heap_table_size
- to reduce the number of disk-based temporary tables
- Note! BLOB and TEXT columns are not allow in memory tables.
- If you are using these columns raising these values might not impact your
- ratio of on disk temp tables.
- TABLE SCANS
- Current read_buffer_size = 2 M
- Current table scan ratio = 10 : 1
- read_buffer_size seems to be fine
- TABLE LOCKING
- Current Lock Wait ratio = 1 : 45460
- Your table locking seems to be fine
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement