[root@server-mysql 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.sh
Resolving www.day32.com... 192.237.221.190
Connecting to www.day32.com|192.237.221.190|:80... connected.
HTTP request sent, awaiting response... 200 OK
Length: 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]

[root@server-mysql mytop-1.6]# chmod +x tuning-primer.sh 
[root@server-mysql mytop-1.6]# ./tuning-primer.sh 

Using login values from ~/.my.cnf
- INITIAL LOGIN ATTEMPT FAILED -
Testing for stored webmin passwords:
 None Found
Could not auto detect login info!
Found potential sockets: /tmp/mysql.sock5
Using: /tmp/mysql.sock5
Would you like to provide a different socket?: [y/N] y
Socket: /tmp/mysql.sock5
Do you have your login handy ? [y/N] : y
User: root
Password: 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_64

Uptime = 0 days 2 hrs 48 min 22 sec
Avg. qps = 0
Total Questions = 892
Threads Connected = 3

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 = 10.000000 sec.
You have 0 out of 913 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.6/en/point-in-time-recovery.html

WORKER THREADS
Current thread_cache_size = 9
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 = 3
Historic max_used_connections = 3
The 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 memory
See "MEMORY USAGE" section to make sure you are not over-allocating

INNODB STATUS
Current InnoDB index space = 1.47 G
Current InnoDB data space = 1.28 G
Current InnoDB buffer pool free = 77 %
Current innodb_buffer_pool_size = 32 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 : 60 M
Configured Max Per-thread Buffers : 169 M
Configured Max Global Buffers : 57 M
Configured Max Memory Limit : 226 M
Physical Memory : 1.30 G
Max memory limit seem to be within acceptable norms

KEY BUFFER
Current MyISAM index space = 118 K
Current key_buffer_size = 8 M
Key cache miss rate is 1 : 16
Key buffer free ratio = 81 %
Your key_buffer_size seems to be fine

QUERY CACHE
Query cache is enabled
Current query_cache_size = 1 M
Current query_cache_used = 16 K
Current query_cache_limit = 1 M
Current Query cache Memory fill ratio = 1.64 %
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
No sort operations have been performed
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 260.00 K
You have had 0 queries where a join could not use an index properly
Your joins seem to be using indexes properly

OPEN FILES LIMIT
Current open_files_limit = 5000 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 = 2000 tables
Current table_definition_cache = 1400 tables
You have a total of 113 tables
You have 117 open tables.
The table_cache value seems to be fine

TEMP TABLES
Current max_heap_table_size = 16 M
Current tmp_table_size = 16 M
Of 1072 temp tables, 6% were created on disk
Created disk tmp tables ratio seems fine

TABLE SCANS
Current read_buffer_size = 128 K
Current table scan ratio = 440 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 0 : 1168
Your table locking seems to be fine