Sitelerimi birkaç gün önce türkiye lokasyon VDS üzerine taşıdım. Şu an yaklaşık 20-30 site mevcut ve ortalama 2-3k hit var. Ancak vbulletin vbseo ve mysql aşırı derecede CPU kullanıyor. MYSQL konusunda tuning-primer.sh kurdum ve 48 saat bekledim. Bu arada sitelerimde bazen db hataları gördüm. Sitelerimde hit olmamasına rağmen aşırı derece bot aktivitesi var. tuning sonuçlarını aşağıda paylaşıyorum yardımcı olursanız sevinirim.
MySQL Version 5.5.40-cll i686
Uptime = 2 days 0 hrs 10 min 17 sec
Avg. qps = 17
Total Questions = 3090502
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/5.5/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 NOT enabled.
Current long_query_time = 10.000000 sec.
You have 55 out of 3090537 that take longer than 10.000000 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.5/en/point-in-time-recovery.html
WORKER THREADS
Current thread_cache_size = 0
Current threads_cached = 0
Current threads_per_sec = 15
Historic threads_per_sec = 0
Threads created per/sec are overrunning threads cached
You should raise thread_cache_size
MAX CONNECTIONS
Current max_connections = 151
Current threads_connected = 6
Historic max_used_connections = 16
The number of used connections is 10% 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 = 146 M
Current InnoDB data space = 674 M
Current InnoDB buffer pool free = 0 %
Current innodb_buffer_pool_size = 128 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 : 195 M
Configured Max Per-thread Buffers : 405 M
Configured Max Global Buffers : 152 M
Configured Max Memory Limit : 557 M
Physical Memory : 14.74 G
Max memory limit seem to be within acceptable norms
KEY BUFFER
Current MyISAM index space = 64 M
Current key_buffer_size = 8 M
Key cache miss rate is 1 : 491
Key buffer free ratio = 88 %
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 1178 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 = 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_open_cache = 400 tables
Current table_definition_cache = 400 tables
You have a total of 1120 tables
You have 400 open tables.
Current table_cache hit rate is 1%
, while 100% of your table cache is in use
You should probably increase your table_cache
You should probably increase your table_definition_cache value.
TEMP TABLES
Current max_heap_table_size = 16 M
Current tmp_table_size = 16 M
Of 227192 temp tables, 42% were created on disk
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 = 1461 : 1
read_buffer_size seems to be fine
TABLE LOCKING
Current Lock Wait ratio = 1 : 32362
Your table locking seems to be fine
my.cnf dosyam
[mysqld]
max_allowed_packet=268435456
open_files_limit=10000
bind-address=127.0.0.1
Bu arada makine özelliklerim 3 çekirdekli AMD 2.1 ghz işlemci ve 16gb ram ve SSD 80 gb disk erişimim var. Yardımlarınız için teşekkürler.
