Tekil Mesaj gösterimi
  #164 (permalink)   iTrader 
Alt 2008-04-18, 09:08
Remark Remark isimli üye çevrimiçidir (Online)
Member
 
Üyelik tarihi: May 2007
Mesajlar: 285
Teşekkür: 0
Thanked 2 Times in 2 Posts
Tecrübe Puanı: 1
iTrader: %0/0
Remark is on a distinguished road
Standart

Merhabalar bende şöyle bir sonuç çıktı.

[root@unix ~]# ./tuning-primer.sh

ls: invalid option -- H
Try `ls --help' for more information.
-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -

MySQL Version 5.0.54 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 = 760
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.0/...variables.html
Visit http://www.mysql.com/products/enterprise/advisors.html
for info about MySQL's Enterprise Monitoring and Advisory Service

ls: invalid option -- H
Try `ls --help' for more information.
SLOW QUERIES
The slow query log is NOT enabled.
Current long_query_time = 10 sec.
You have 0 out of 781 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/5.0/...-recovery.html

WORKER THREADS
Current thread_cache_size = 0
Current threads_cached = 0
Current threads_per_sec = 1
Historic threads_per_sec = 0
Your thread_cache_size is fine

MAX CONNECTIONS
Current max_connections = 100
Current threads_connected = 1
Historic max_used_connections = 1
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

ls: invalid option -- H
Try `ls --help' for more information.
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 : 18
Key buffer fill ratio = %
./tuning-primer.sh: line 680: [: -ge: unary operator expected
./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
Query cache is supported but not enabled
Perhaps you should set the query_cache_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 = K
You have had 0 queries where a join could not use an index properly
Your joins seem to be using indexes properly

ls: invalid option -- H
Try `ls --help' for more information.
OPEN FILES LIMIT
Current open_files_limit = 1024 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 = 64 tables
You have a total of 528 tables
You have 64 open tables.
Current table_cache hit rate is 10%, while 100% 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 116 temp tables, 10% 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 = K
Current table scan ratio = 637 : 1
read_buffer_size seems to be fine

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

[root@unix ~]#
Alıntı ile Cevapla