-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -
MySQL Version 4.1.22-standard i686
./tuning-primer.sh: line 388: bc: command not found
./tuning-primer.sh: line 389: bc: command not found
./tuning-primer.sh: line 390: bc: command not found
./tuning-primer.sh: line 391: bc: command not found
./tuning-primer.sh: line 392: bc: command not found
./tuning-primer.sh: line 393: bc: command not found
Uptime = days hrs min sec
Avg. qps = 5
Total Questions = 1707329
Threads Connected = 1
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/4.1/...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 sec.
You have 99 out of 1707343 that take longer than 10 sec. to complete
Your long_query_time may be too high, I typically set this under 5 sec.
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/4.1/...-recovery.html
WORKER THREADS
Current thread_cache_size = 128
Current threads_cached = 85
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine
MAX CONNECTIONS
Current max_connections = 500
Current threads_connected = 1
Historic max_used_connections = 86
The number of used connections is 17% of the configured maximum.
Your max_connections variable seems to be fine.
MEMORY USAGE
./tuning-primer.sh: line 1204: bc: command not found
./tuning-primer.sh: line 1205: bc: command not found
./tuning-primer.sh: line 1229: bc: command not found
./tuning-primer.sh: line 1232: bc: command not found
./tuning-primer.sh: line 1233: bc: command not found
./tuning-primer.sh: line 1235: bc: command not found
./tuning-primer.sh: line 1237: [: -gt: unary operator expected
./tuning-primer.sh: line 350: [: max_memoryHR: integer expression expected
./tuning-primer.sh: line 356: [: max_memoryHR: integer expression expected
./tuning-primer.sh: line 362: [: max_memoryHR: integer expression expected
./tuning-primer.sh: line 369: export: `0=max_memoryHR': not a valid identifier
Max Memory Ever Allocated : bytes
./tuning-primer.sh: line 350: [: per_thread_buffersHR: integer expression expected
./tuning-primer.sh: line 356: [: per_thread_buffersHR: integer expression expected
./tuning-primer.sh: line 362: [: per_thread_buffersHR: integer expression expected
./tuning-primer.sh: line 369: export: `0=per_thread_buffersHR': not a valid identifier
Configured Max Per-thread Buffers : bytes
./tuning-primer.sh: line 350: [: global_buffersHR: integer expression expected
./tuning-primer.sh: line 356: [: global_buffersHR: integer expression expected
./tuning-primer.sh: line 362: [: global_buffersHR: integer expression expected
./tuning-primer.sh: line 369: export: `0=global_buffersHR': not a valid identifier
Configured Max Global Buffers : bytes
./tuning-primer.sh: line 350: [: total_memoryHR: integer expression expected
./tuning-primer.sh: line 356: [: total_memoryHR: integer expression expected
./tuning-primer.sh: line 362: [: total_memoryHR: integer expression expected
./tuning-primer.sh: line 369: export: `0=total_memoryHR': not a valid identifier
Configured Max Memory Limit : bytes
./tuning-primer.sh: line 331: bc: command not found
Physical Memory : G
Max memory limit seem to be within acceptable norms
KEY BUFFER
./tuning-primer.sh: line 331: bc: command not found
./tuning-primer.sh: line 646: bc: command not found
./tuning-primer.sh: line 647: bc: command not found
./tuning-primer.sh: line 331: bc: command not found
Current MyISAM index space = M
./tuning-primer.sh: line 331: bc: command not found
Current key_buffer_size = M
Key cache miss rate is 1 : 521
Key buffer fill ratio = %
./tuning-primer.sh: line 684: [: -ge: unary operator expected
./tuning-primer.sh: line 688: [: -le: unary operator expected
Your key_buffer_size seems to be fine
QUERY CACHE
./tuning-primer.sh: line 719: bc: command not found
./tuning-primer.sh: line 720: bc: command not found
Query cache is enabled
./tuning-primer.sh: line 331: bc: command not found
Current query_cache_size = M
./tuning-primer.sh: line 331: bc: command not found
Current query_cache_used = M
./tuning-primer.sh: line 331: bc: command not found
Current query_cache_limit = M
Current Query cache Memory fill ratio = %
./tuning-primer.sh: line 331: bc: command not found
Current query_cache_min_res_unit = K
./tuning-primer.sh: line 733: bc: command not found
./tuning-primer.sh: line 734: bc: command not found
./tuning-primer.sh: line 735: [: -gt: unary operator expected
./tuning-primer.sh: line 742: [: -le: unary operator expected
./tuning-primer.sh: line 746: [: -ge: unary operator expected
MySQL won't cache query results that are larger than query_cache_limit in size
SORT OPERATIONS
./tuning-primer.sh: line 331: bc: command not found
Current sort_buffer_size = M
./tuning-primer.sh: line 331: bc: command not found
Current read_rnd_buffer_size = K
Sort buffer seems to be fine
JOINS
./tuning-primer.sh: line 331: bc: command not found
Current join_buffer_size = M
You have had 31 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 = 2558 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_cache value = 1024 tables
You have a total of 1650 tables
You have 1022 open tables.
Current table_cache hit rate is 11%, while 99% of your table cache is in use
You should probably increase your table_cache
TEMP TABLES
./tuning-primer.sh: line 331: bc: command not found
Current max_heap_table_size = M
./tuning-primer.sh: line 331: bc: command not found
Current tmp_table_size = M
Of 91866 temp tables, 0% were created on disk
Effective in-memory tmp_table_size is limited to max_heap_table_size.
Created disk tmp tables ratio seems fine
TABLE SCANS
./tuning-primer.sh: line 331: bc: command not found
Current read_buffer_size = M
Current table scan ratio = 2109 : 1
read_buffer_size seems to be fine
TABLE LOCKING
Current Lock Wait ratio = 1 : 979
You may benefit from selective use of InnoDB.
If you have long running SELECT's against MyISAM tables and perform
frequent updates consider setting 'low_priority_updates=1'
Böyle bir çıktı aldım nasıl bir yol izlemem lazım yardımcı olursan sevinirim iyinet.