Advertisement
Not a member of Pastebin yet?
Sign Up,
it unlocks many cool features!
- -- MYSQL PERFORMANCE TUNING PRIMER --
- - By: Matthew Montgomery -
- MySQL Version 5.6.19-67.0-log x86_64
- Uptime = 0 days 0 hrs 16 min 32 sec
- Avg. qps = 0
- Total Questions = 208
- Threads Connected = 1
- Warning: Server has not been running for at least 48hrs.
- It may not be safe to use these recommendations
- To find out more information on how each of these
- runtime variables effects performance visit:
- http://dev.mysql.com/doc/refman/5.6/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 = 60.000000 sec.
- You have 17 out of 229 that take longer than 60.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.6/en/point-in-time-recovery.html
- WORKER THREADS
- Current thread_cache_size = 20
- Current threads_cached = 0
- Current threads_per_sec = 0
- Historic threads_per_sec = 0
- Your thread_cache_size is fine
- MAX CONNECTIONS
- Current max_connections = 151
- Current threads_connected = 1
- Historic max_used_connections = 1
- The number of used connections is 0% 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 = 7.04 G
- Current InnoDB data space = 8.09 G
- Current InnoDB buffer pool free = 99 %
- Current innodb_buffer_pool_size = 4.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 : 5.07 G
- Configured Max Per-thread Buffers : 29.59 G
- Configured Max Global Buffers : 4.88 G
- Configured Max Memory Limit : 34.47 G
- Physical Memory : 15.67 G
- Max memory limit exceeds 90% of physical memory
- KEY BUFFER
- No key reads?!
- Seriously look into using some indexes
- Current MyISAM index space = 1.81 G
- Current key_buffer_size = 128 M
- Key cache miss rate is 1 : 0
- Key buffer free ratio = 81 %
- Your key_buffer_size seems to be fine
- QUERY CACHE
- Query cache is enabled
- Current query_cache_size = 512 M
- Current query_cache_used = 17 K
- Current query_cache_limit = 256 M
- Current Query cache Memory fill ratio = 0 %
- Current query_cache_min_res_unit = 4 K
- Your query_cache_size seems to be too high.
- Perhaps you can use these resources elsewhere
- MySQL won't cache query results that are larger than query_cache_limit in size
- SORT OPERATIONS
- Current sort_buffer_size = 256 K
- Current read_rnd_buffer_size = 256 K
- Sort buffer seems to be fine
- JOINS
- Current join_buffer_size = 192.00 M
- You have had 0 queries where a join could not use an index properly
- Your joins seem to be using indexes properly
- join_buffer_size >= 4 M
- This is not advised
- OPEN FILES LIMIT
- Current open_files_limit = 20162 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 = 10000 tables
- Current table_definition_cache = 2000 tables
- You have a total of 238 tables
- You have 238 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 749 temp tables, 11% were created on disk
- Created disk tmp tables ratio seems fine
- TABLE SCANS
- Current read_buffer_size = 8 M
- Current table scan ratio = 27 : 1
- read_buffer_size seems to be fine
- TABLE LOCKING
- Current Lock Wait ratio = 0 : 484
- Your table locking seems to be fine
Advertisement
Add Comment
Please, Sign In to add comment
Advertisement