|
MYSQL PERFORMANCE TUNING PRIMER
라는 툴을 받아서 설치후에 설정파일 설정 변경해가면서 최적 값을 찾아보려고 노력중인데..
어려움이 많아서 도움좀 요청 드립니다... 프로그램 설명을 보니 색깔로 표시되는 권고사항을 신경써서 보라고 해서
값도 변경해보고 추가도 해보고 하는데... 새로 설정 변경하고 실행해봐도 저 색깔있는 내용들이 변함이 없어서요..
멀 잘못한건지... 멀 손봐야 하는건지 좀 알려주시면 정말 감사하겠습니다.. 특히 저 max_connection 관련해서 빨간색으로
나오는 부분은 멀 어떻게 하라는건지 모르겠네요.. 부탁드립니다..
[user@localhost ~]# ./tuning-primer.sh
-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -
MySQL Version 5.0.77-log x86_64
Uptime = 0 days 0 hrs 0 min 45 sec
Avg. qps = 246
Total Questions = 11112
Threads Connected = 10
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.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 enabled.
Current long_query_time = 1 sec.
You have 0 out of 11137 that take longer than 1 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.0/en/point-in-time-recovery.html
WORKER THREADS
Current thread_cache_size = 50
Current threads_cached = 7
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine
MAX CONNECTIONS
Current max_connections = 300
Current threads_connected = 8
Historic max_used_connections = 16
The number of used connections is 5% 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 = 288 K
Current InnoDB data space = 176 K
Current InnoDB buffer pool free = 89 %
Current innodb_buffer_pool_size = 8 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 : 1.11 G
Configured Max Per-thread Buffers : 1.94 G
Configured Max Global Buffers : 1.00 G
Configured Max Memory Limit : 2.95 G
Physical Memory : 3.84 G
Max memory limit seem to be within acceptable norms
KEY BUFFER
Current MyISAM index space = 1.50 G
Current key_buffer_size = 1.00 G
Key cache miss rate is 1 : 302
Key buffer free ratio = 80 %
Your key_buffer_size seems to be fine
QUERY CACHE
Query cache is supported but not enabled
Perhaps you should set the query_cache_size
SORT OPERATIONS
Current sort_buffer_size = 2 M
Current read_rnd_buffer_size = 256 K
Sort buffer seems to be fine
JOINS
Current join_buffer_size = 132.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 = 2358 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 543 tables
You have 565 open tables.
The table_cache value seems to be fine
TEMP TABLES
Current max_heap_table_size = 16 M
Current tmp_table_size = 32 M
Of 647 temp tables, 11% 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
Current read_buffer_size = 4 M
Current table scan ratio = 2668 : 1
read_buffer_size seems to be fine
TABLE LOCKING
Current Lock Wait ratio = 1 : 2842
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'
If you have a high concurrency of inserts on Dynamic row-length tables
consider setting 'concurrent_insert=2'.
|
