Tekil Mesaj gösterimi
  #17 (permalink)   iTrader 
Alt 2007-12-27, 22:05
Mywedding Mywedding isimli üyemiz çevrimdışıdır. (Offline)
mami
 
Üyelik tarihi: Sep 2006
Nerden: dreamcity
Mesajlar: 4.309
Blog Entries: 3
Teşekkür: 0
Thanked 0 Times in 0 Posts
Tecrübe Puanı: 0
iTrader: %100/18
Mywedding is just really niceMywedding is just really niceMywedding is just really niceMywedding is just really nice
Standart

Alıntı:
estranged´isimli üyeden Alıntı Mesajı göster
Şimdilik 8-10 MB yetecektir ama mysql verilerinizin büyüme hızına bağlı olarak ne kadar süre yeteceği değişir, düzenli olarak kontrol edip ona göre ayarlama yapmak gerekir. En iyisi tuning-premier.sh ile bakıp tüm ayarları oradaki verilere göre yapmak.
-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -

MySQL Version 5.0.27 i686

Uptime = 15 days 2 hrs 46 min 50 sec
Avg. qps = 34
Total Questions = 45383444
Threads Connected = 5

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

SLOW QUERIES
Current long_query_time = 10 sec.
You have 603 out of 45383538 that take longer than 10 sec. to complete
The slow query log is NOT enabled.
Your long_query_time may be too high, I typically set this under 5 sec.

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

MAX CONNECTIONS
Current max_connections = 650
Current threads_connected = 8
Historic max_used_connections = 46
The number of used connections is 7% 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

MEMORY USAGE
Max Memory Ever Allocated : 327 M
Configured Max Per-thread Buffers : 2 G
Configured Max Global Buffers : 170 M
Configured Max Memory Limit : 2 G
Physical Memory : 1.48 G

Max memory limit exceeds 90% of physical memory

KEY BUFFER
Current MyISAM index space = 5 M
Current key_buffer_size = 128 M
Key cache miss rate is 1 : 59115
Key buffer fill ratio = 2.00 %
Your key_buffer_size seems to be too high.
Perhaps you can use these resources elsewhere

QUERY CACHE
Query cache is enabled
Current query_cache_size = 32 M
Current query_cache_used = 11 M
Current query_cache_limit = 4 M
Current Query cache Memory fill ratio = 34.78 %
Current query_cache_min_res_unit = 4 K
Query Cache is 15 % fragmented
Run "FLUSH QUERY CACHE" periodically to defragment the query cache memory
If you have many small queries lower 'query_cache_min_res_unit' to reduce fragmentation.
MySQL won't cache query results that are larger than query_cache_limit in size

SORT OPERATIONS
Current sort_buffer_size = 2 M
Current record/read_rnd_buffer_size = 1020 K
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 132.00 K
You have had 1703 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 = 3660 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 = 1500 tables
You have a total of 315 tables
You have 377 open tables.
The table_cache value seems to be fine

TEMP TABLES
Current max_heap_table_size = 255 M
Current tmp_table_size = 256 M
Of 178556 temp tables, 68% were created on disk
Effective in-memory tmp_table_size is limited to max_heap_table_size.
Perhaps you should increase your tmp_table_size and/or max_heap_table_size
to reduce the number of disk-based temporary tables
Note! BLOB and TEXT columns are not allow in memory tables.
If you are using these columns raising these values might not impact your
ratio of on disk temp tables.

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

TABLE LOCKING
Current Lock Wait ratio = 1 : 544
You may benefit from selective use of InnoDB.
If you have a high concurrency of inserts on Dynamic row-length tables
consider setting 'concurrent_insert=2'.

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