tuning-primer.sh mysql tuning scripti - mysql performans raporu

iyinet

Müptela Üye
Yönetici
Administratör
Katılım
2 Eyl 2002
Mesajlar
5,019
Beğeniler
47
Konum
Gaziantep
#1
mysql optimizastonu için tuning-primer.sh scriptini indirmenizi öneririm.
ssh de çalıştırabileceğiniz bu script mysql ayarlarınızı kontrol edip tavsiyede bulunuyor.

scriptin adı: tuning-primer.sh
scriptin bulunduğu site: http://day32.com/MySQL/
doğrudan link: http://day32.com/MySQL/tuning-primer.sh

ssh de çalıştırmak için:
# wget http://day32.com/MySQL/tuning-primer.sh
# chmod u+x tuning-primer.sh
# ./tuning-primer.sh

! scripti mysql i başlatmanızın ardından minmum 2 gün sonra çalıştırınız, aksi taktirde veriler tutarsız olabilir.


Çıktı bu şekilde, takıldığınız yer olursa ekran çıktınızı buraya ekleyin yorumlamanıza yardımcı olalım.


# ./tuning-primer.sh

MySQL Version 4.1.22-standard i686

Uptime = 0 days 0 hrs 4 min 15 sec
Avg. qps = 17
Total Questions = 4479
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/4.1/...variables.html

SLOW QUERIES
Current long_query_time = 10 sec.
You have 1 out of 4491 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 = 128
Current threads_cached = 6
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine

MAX CONNECTIONS
Current max_connections = 2000
Current threads_connected = 1
Historic max_used_connections = 7
The number of used connections is 0% 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 : 96 M
Configured Max Per-thread Buffers : 10 G
Configured Max Global Buffers : 58 M
Configured Max Memory Limit : 10 G
Total System Memory : 3.95 G

Max memory limit exceeds 85% of total system memory

KEY BUFFER
Current MyISAM index space = 78 M
Current key_buffer_size = 16 M
Key cache miss rate is 1 : 735
Key buffer fill ratio = 8.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 = 4 M
Current query_cach_limit = 1 M
Current Query cache fill ratio = 14.83 %
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 = 2 M
Current record/read_rnd_buffer_size = 256 K
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 1.00 M
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 = 10000 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 721 tables
You have 93 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 212 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
Current read_buffer_size = 1 M
Current table scan ratio = 17754 : 1
You have a high ratio of sequential access requests to SELECTs
You may benefit from raising read_buffer_size and/or improving your use of indexes.

TABLE LOCKING
Current Lock Wait ratio = 1 : 76
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'

#
 

CaLViN

Onursal
Onursal Üye
Katılım
25 Kas 2004
Mesajlar
7,488
Beğeniler
63
Konum
Ankara
#4
Merhaba,
ssh de çalıştırabileceğiniz bu script mysql ayarlarınızı kontrol edip tavsiyede bulunuyor.
e-mail mi atıyor,sistemde log mu tutuyor yada otomatik olarak ayarları mı uyguluyor ?
 

elmasgunes

Müptela Üye
Katılım
27 Ocak 2004
Mesajlar
1,443
Beğeniler
0
#7
Teşekkürler iyinet.

MySQL optimizasyonu konusunda gayet yararlı bilgiler veriyor. Buradaki önerilere göre MySQL'i optimize etmeniz sitenizin açılış hızını kat ve kat artıracaktır.
 

Loi

Müptela Üye
Katılım
13 Kas 2006
Mesajlar
6,213
Beğeniler
43
Konum
localhost
#8
TABLE CACHE
Current table_cache value = 64 tables
You have a total of 385 tables
You have 64 open tables.
Current table_cache hit rate is 0%, while 100% of your table cache is in use
You should probably increase your table_cache
Bunun disinda herseye fine diyor, nedir bu ve bunu nasil yukseltebilirim?
 

elmasgunes

Müptela Üye
Katılım
27 Ocak 2004
Mesajlar
1,443
Beğeniler
0
#12
385 mi yoksa 512 mi karar verin :)
Şu andaki tablo sayın 385. O yüzden 385 yapman daha iyi olabilir. Ancak ileride genişleteceğin tablolar için de o sayıyı artırman performans açısından yararlı olabilir.

Ben kendi sunucumda kullandığım sayı ile göndermiştim.
 

Loi

Müptela Üye
Katılım
13 Kas 2006
Mesajlar
6,213
Beğeniler
43
Konum
localhost
#13
Tamamdir tesekkurler arkadaslar ;)

Konu optimizasyondan acilmisken deyinmek istiyorum.

benim serverda veriler cok hizli geliyor şak diye ekranda oluyor ancak grafiklerin ekrana gelişi cok zaman aliyor boyutlari gercekten cok kucuk olmalarina ragmen boyle. Bununla ilgili bir onerisi olan varmi?
 

i.ari

Müptela Üye
Katılım
16 Ara 2006
Mesajlar
4,445
Beğeniler
6
Konum
Ankara
#15
Bende cıkanlar.


-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -

MySQL Version 4.1.20 i686

Uptime = 21 days 10 hrs 51 min 4 sec
Avg. qps = 25
Total Questions = 47386472
Threads Connected = 2

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/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
Current long_query_time = 10 sec.
You have 11082 out of 47386484 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 = 0
Current threads_cached = 0
Current threads_per_sec = 3
Historic threads_per_sec = 2
Threads created per/sec are overrunning threads cached
You should raise thread_cache_size

MAX CONNECTIONS
Current max_connections = 300
Current threads_connected = 1
Historic max_used_connections = 57
The number of used connections is 19% of the configured maximum.
Your max_connections variable seems to be fine.

MEMORY USAGE
Max Memory Ever Allocated : 203 M
Configured Max Per-thread Buffers : 806 M
Configured Max Global Buffers : 49 M
Configured Max Memory Limit : 856 M
Physical Memory : 1001.19 M
Max memory limit seem to be within acceptable norms

KEY BUFFER
Current MyISAM index space = 74 M
Current key_buffer_size = 7 M
Key cache miss rate is 1 : 92
Key buffer fill ratio = 93.00 %
You could increase key_buffer_size
It is safe to raise this up to 1/4 of total system memory;
assuming this is a dedicated database server.

QUERY CACHE
Query cache is enabled
Current query_cache_size = 32 M
Current query_cache_used = 22 M
Current query_cache_limit = 1 M
Current Query cache Memory fill ratio = 69.99 %
Current query_cache_min_res_unit = 4 K
Query Cache is 13 % 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 = 256 K
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 132.00 K
You have had 470 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 = 1510 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 440 tables
You have 64 open tables.
Current table_cache hit rate is 0%, while 100% of your table cache is in use
You should probably increase your table_cache

TEMP TABLES
Current max_heap_table_size = 16 M
Current tmp_table_size = 32 M
Of 2803661 temp tables, 21% 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 = 128 K
Current table scan ratio = 350 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 1 : 1071
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'
 

iyinet

Müptela Üye
Yönetici
Administratör
Katılım
2 Eyl 2002
Mesajlar
5,019
Beğeniler
47
Konum
Gaziantep
#16
i.ari, my.cnf içindeki değerleri bu şekilde değiştir, değişken yoksa ekle.

thread_cache_size = 384
max_connections = 200
key_buffer = 128M
query_cache_limit = 4M
table_cache = 450
low_priority_updates = 1
 

i.ari

Müptela Üye
Katılım
16 Ara 2006
Mesajlar
4,445
Beğeniler
6
Konum
Ankara
#18
3.x lerde olan cpu kullanımı 0,2x-0,3x lere düştü :S

Bu kadar fark tesadüfmü yoksa cokmu önemli idi bu degişikler bilmiyorum :)
 

iyinet

Müptela Üye
Yönetici
Administratör
Katılım
2 Eyl 2002
Mesajlar
5,019
Beğeniler
47
Konum
Gaziantep
#19
3.x lerde olan cpu kullanımı 0,2x-0,3x lere düştü :S

Bu kadar fark tesadüfmü yoksa cokmu önemli idi bu degişikler bilmiyorum :)
Tesadüf değil elbette.
Yardım ettikçe o kadar çok ayarsız mysql * php * apache görüyorum ki, onlara harcanan CPU lara yazık diyorum.
 

i.ari

Müptela Üye
Katılım
16 Ara 2006
Mesajlar
4,445
Beğeniler
6
Konum
Ankara
#20
Buda başka bir sunucu:

-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -

MySQL Version 4.0.25 is EOL please upgrade to MySQL 4.1 or later

Uptime = 11 days 18 hrs 53 min 23 sec
Avg. qps = 9
Total Questions = 10099373
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/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
Current long_query_time = 10 sec.
You have 129 out of 10099385 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 = 100
Current threads_cached = 54
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 = 1
Historic max_used_connections = 54
The number of used connections is 18% of the configured maximum.
Your max_connections variable seems to be fine.

MEMORY USAGE
Max Memory Ever Allocated : 131 M
Configured Max Per-thread Buffers : 316 M
Configured Max Global Buffers : 74 M
Configured Max Memory Limit : 390 M
Physical Memory : 501.48 M
Max memory limit seem to be within acceptable norms

KEY BUFFER
Current MyISAM index space = 66 M
Current key_buffer_size = 512 K
Key cache miss rate is 1 : 21
Key buffer fill ratio = Unknown %
Your key_buffer_size seems to be fine

QUERY CACHE
Query cache is enabled
Current query_cache_size = 64 M
Current query_cache_used = 47 M
Current query_cache_limit = 1 M
Current Query cache Memory fill ratio = 74.51 %
./tuning-primer.sh: line 345: [: query_cache_min_res_unitHR: integer expression expected
./tuning-primer.sh: line 351: [: query_cache_min_res_unitHR: integer expression expected
./tuning-primer.sh: line 357: [: query_cache_min_res_unitHR: integer expression expected
./tuning-primer.sh: line 364: export: `=query_cache_min_res_unitHR': not a valid identifier
Current query_cache_min_res_unit = bytes
Query Cache is 13 % 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 = 100 K
Current record/read_rnd_buffer_size = 256 K
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 132.00 K
You have had 526 queries where a join could not use an index properly
You should enable "log-long-format"
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 = 1510 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 1597 tables
You have 64 open tables.
Current table_cache hit rate is 0%, while 100% of your table cache is in use
You should probably increase your table_cache

TEMP TABLES
Current max_heap_table_size = 16 M
Current tmp_table_size = 32 M
Of 146715 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 = 96 K
Current table scan ratio = 1248 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 1 : 1604
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'
 

Bu konuyu okuyanlar (Üyeler: 1, Misafirler: 0)

Üst