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

[3fsane]

Teşekkürler iyinet

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

MySQL Version 4.1.22-standard i686

Uptime = 3 days 4 hrs 44 min 25 sec
Avg. qps = 58
Total Questions = 16246651
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/...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 2809 out of 16246663 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 = 5
Historic threads_per_sec = 2
Threads created per/sec are overrunning threads cached
You should raise thread_cache_size

MAX CONNECTIONS
Current max_connections = 500
Current threads_connected = 2
Historic max_used_connections = 150
The number of used connections is 30% of the configured maximum.
Your max_connections variable seems to be fine.

MEMORY USAGE
Max Memory Ever Allocated : 421 M
Configured Max Per-thread Buffers : 1 G
Configured Max Global Buffers : 17 M
Configured Max Memory Limit : 1 G
Physical Memory : 1.97 G
Max memory limit seem to be within acceptable norms

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

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 record/read_rnd_buffer_size = 256 K
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 132.00 K
You have had 60423 queries where a join could not use an index properly
You have had 190 joins without keys that check for key usage after each row
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 = 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 = 64 tables
You have a total of 15106 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 1012201 temp tables, 12% 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 = 179 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 1 : 5196
Your table locking seems to be fine

Sunucu ;
Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
2 GB RAM

[iyinet]

3fsane´isimli üyeden Alıntı

Teşekkürler iyinet

Sunucu ;
Intel(R) Core(TM)2 CPU 6600 @ 2.40GHz
2 GB RAM

Bu ayarları yap, yoksa ekle varsa bu şekilde değiştir, bunlar sadece [mysqld] altına girecek.

skip-locking
skip-name-resolve
max_connections = 300
thread_cache_size = 128
key_buffer = 128M
query_cache_type = 1
query_cache_size = 32M
query_cache_limit = 4M
table_cache = 30000
low_priority_updates = 1

Dikkatimi çeken ya henüz bu db üzerinde uygulama çalışmıyor yada indexler kullanılamıyor.

[3fsane]

iyinet´isimli üyeden Alıntı

Bu ayarları yap, yoksa ekle varsa bu şekilde değiştir, bunlar sadece [mysqld] altına girecek.

Dikkatimi çeken ya henüz bu db üzerinde uygulama çalışmıyor yada indexler kullanılamıyor.

Bu Şekildeydi.

[mysqld]
set-variable = max_connections=500
safe-show-database

Bu şekilde değiştirdim, umarım doğrudur.

[mysqld]
skip-locking
skip-name-resolve
max_connections = 300
thread_cache_size = 128
key_buffer = 128M
query_cache_type = 1
query_cache_size = 32M
query_cache_limit = 4M
table_cache = 30000
low_priority_updates = 1
set-variable = max_connections=500
safe-show-database

4-5 Forum DB si aktif olarak çalışıyor..

[iyinet]

3fsane´isimli üyeden Alıntı

Bu Şekildeydi.




Bu şekilde değiştirdim, umarım doğrudur.


4-5 Forum DB si aktif olarak çalışıyor..

bu satırı kaldır:

set-variable = max_connections=500

[3fsane]

Kaldırıp mysql i restartladım, Teşekkürler

[iyinet]

vbulletin ve vbseo kullanan PHP kullanıcılarına memcached kurmalarını öneririm, yükde %30-50 lere kadar varan bir düşüş oluyor.
sar ile baktığımızda eskiden 20 lerde olan server kullanıcı yükü 10-15 ler arasında dolaşıyor.

$ sar

       CPU     %user     %nice   %system   %iowait     %idle
       all      12.21      0.00      0.88      0.73     86.18

Özellikle vbseo memcached den oldukça iyi faydalanıyor.

[3fsane]

Başka bir sunucum için my.cnf ayarı alabilirmiyim ?

-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -
MySQL Version 4.1.22-standard i686
Uptime = 37 days 0 hrs 17 min 15 sec
Avg. qps = 20
Total Questions = 64850071
Threads Connected = 4
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
Current long_query_time = 10 sec.
You have 11263 out of 64850083 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 = 1
Threads created per/sec are overrunning threads cached
You should raise thread_cache_size
MAX CONNECTIONS
Current max_connections = 500
Current threads_connected = 4
Historic max_used_connections = 148
The number of used connections is 29% of the configured maximum.
Your max_connections variable seems to be fine.
MEMORY USAGE
Max Memory Ever Allocated : 415 M
Configured Max Per-thread Buffers : 1 G
Configured Max Global Buffers : 17 M
Configured Max Memory Limit : 1 G
Physical Memory : 1.97 G
Max memory limit seem to be within acceptable norms
KEY BUFFER
Current MyISAM index space = 649 M
Current key_buffer_size = 7 M
Key cache miss rate is 1 : 97
Key buffer fill ratio = 100.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 supported but not enabled
Perhaps you should set the query_cache_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 6465 queries where a join could not use an index properly
You have had 12 joins without keys that check for key usage after each row
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 = 4096 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 2403 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 2117988 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 = 128 K
Current table scan ratio = 19 : 1
read_buffer_size seems to be fine
TABLE LOCKING
Current Lock Wait ratio = 1 : 1192
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'

Sunucu ;
Intel(R) Pentium(R) 4 CPU 3.60GHz
2 GB RAM

[iyinet]

3fsane´isimli üyeden Alıntı

Başka bir sunucum için my.cnf ayarı alabilirmiyim ?



Sunucu ;
Intel(R) Pentium(R) 4 CPU 3.60GHz
2 GB RAM

Bu ayarları yapın, değerler yoksa ekleyin varsa bu şekilde değiştirin, bunlar sadece [mysqld] altına eklenecek.

skip-locking
skip-name-resolve
max_connections = 300
thread_cache_size = 128
key_buffer = 256M
query_cache_type = 1
query_cache_size = 32M
query_cache_limit = 4M
table_cache = 5000
low_priority_updates = 1

[3fsane]

iyinet´isimli üyeden Alıntı

Bu ayarları yapın, değerler yoksa ekleyin varsa bu şekilde değiştirin, bunlar sadece [mysqld] altına eklenecek.

skip-locking
skip-name-resolve
max_connections = 300
thread_cache_size = 128
key_buffer = 256M
query_cache_type = 1
query_cache_size = 32M
query_cache_limit = 4M
table_cache = 5000
low_priority_updates = 1

Teşekkürler aynen yaptım..

Bu gerekli ayarlamayı yaptıkdan sonra tuning-primer.sh yi kaldırmamız gerekiyor mu ? Evetse nasıl kaldıracağız ?

[iyinet]

3fsane´isimli üyeden Alıntı

Teşekkürler aynen yaptım..

Bu gerekli ayarlamayı yaptıkdan sonra tuning-primer.sh yi kaldırmamız gerekiyor mu ? Evetse nasıl kaldıracağız ?

Hayır kaldırmanıza gerek yok, o zaten ufak bir script sadece, çalıştırılmadıkça sistem kaynağı kullanan birşey değil.

Hatta ayda bir çalıştırıp sonuçlara bakın.