![]() |
|
|||||||
| MySQL Veritabanı SQL SQL MySQL Access MSSQL Oracle Veritabani Database |
![]() |
|
|
LinkBack (10) | Seçenekler | Stil |
|
|||
|
Anlamlarını bilmiyorum
Onlar ekli idi. Extra bir şey yapmadım. Benim için gerekli olanlar hangileri acaba. Birde fazlalıkları silip öyle denemek istiyorum. Tekrardan teşekkürler. |
|
|||
|
Özellikle TempTables e Asılı kaldım... Birde Keybuffer konusunda kararsız kaldım...
Ram kullanımı nerdeyse tamamen kullanılıyor durumda gibi... Loadlar en fazla 5 lere çıkıyor... Yogun zamanlarda tabi... Normal zamanlarda 1-2 lerde seyrediyor.. Xeon 2.8 ve 4 GB Ram var... Yorum yapabilirsen sevinirim iyinet... Şimdiden Teşekkürler... Kod:
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 = 3 sec. You have 22758 out of 83813621 that take longer than 3 sec. to complete The slow query log is NOT enabled. Your long_query_time seems to be fine WORKER THREADS Current thread_cache_size = 100 Current threads_cached = 84 Current threads_per_sec = 0 Historic threads_per_sec = 0 Your thread_cache_size is fine MAX CONNECTIONS Current max_connections = 150 Current threads_connected = 4 Historic max_used_connections = 88 The number of used connections is 58% of the configured maximum. Your max_connections variable seems to be fine. MEMORY USAGE Max Memory Ever Allocated : 1 G Configured Max Per-thread Buffers : 2 G Configured Max Global Buffers : 42 M Configured Max Memory Limit : 2 G Physical Memory : 3.95 G Max memory limit seem to be within acceptable norms KEY BUFFER Current MyISAM index space = 642 M Current key_buffer_size = 512 K Key cache miss rate is 1 : 35 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 enabled Current query_cache_size = 32 M Current query_cache_used = 20 M Current query_cache_limit = 4 M Current Query cache Memory fill ratio = 63.49 % 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 = 4 M Sort buffer seems to be fine JOINS Current join_buffer_size = 132.00 K You have had 3083 queries where a join could not use an index properly You have had 1 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 = 65535 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 = 32687 tables You have a total of 3784 tables You have 4281 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 309914 temp tables, 36% 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 = 7 M Current table scan ratio = 15 : 1 read_buffer_size seems to be fine TABLE LOCKING Current Lock Wait ratio = 1 : 895 You may benefit from selective use of InnoDB. |
|
|||
|
Selam iyinet bunuda verirsen cok sevinirim..
Kod:
Mysql çok kullanılıyor load yogun oldugu zamanlarda 10 ve üstüne cıkabılıyor. Makina özellikleri AMD Opteron 1212 (Dual Core) 3 GB DDR2-Ram Cpanel / WHM .. Alıntı:
my.cnf Dosyası içeriği ; Kod:
[mysqld] datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock skip-innodb skip-locking local-infile=0 safe-show-database max_connections = 500 max_user_connections = 400 key_buffer = 384M sort_buffer_size = 2M read_buffer_size = 2M read_rnd_buffer_size = 8M myisam_sort_buffer_size = 64M table_cache = 8500 tmp_table_size = 40M low_priority_updates = 1 max_allowed_packet = 8M thread_cache_size = 8 query_cache_size = 32M query_cache_type = 1 Konu C0$kuN tarafından (2008-02-04 Saat 00:17 ) değiştirilmiştir.. |
|
|||
|
merhaba iyinet, şuna bakabilirmisin,
Alıntı:
|
|
|||
|
Peki kısa bi soru sorsam vaktin olursa yazabilirsen sevinirim..
FLUSH QUERY CACHE hakkında pek anlayacagım bi döküman bulamadım... Çok uzun değil ise bi yol gösterebilirsen sevinirim... Birde bu scriptte temp tables olarak bahsettiği şeyi neye göre görüyor acaba... Temp olarak bahsettiği şey nerdedir... |
|
||||
|
Aslında burada bir anlatım var: http://dev.mysql.com/doc/refman/5.0/...intenance.html
Özetlemek gerekirse, FLUSH QUEY CACHE query cache içindeki fragmantasyonu (parçalı boşlukları) gideriyor. Faydalı bir komut, örneğin günde 1 kez bunu yapmanız query cache performansını arttırabilir. MySQL de temp tables konusunu tam hatırlamıyorum, sanki internal olarak tam mğdahale edilemiyor diye hatırlıyorum, ama kısaca o da MySQL in kendi işlerini yapmakta kullandığı bir alan. Sort, group by falan işlemlerini, büyük joinleri burada yapıyor diye hatırlıyorum. Vaktim olunca biraz okuyup buraya yazarım. |
|
|||
|
Core2 Duo 2.66 GHZ
2 GB RAM Yardımcı olursanız çok memnun olurum. Bazı noktalarda kırmızı olan bölümler var. Daha iyi bi sonuç için neleri değiştirmemi önerirsiniz. Teşekkürler arkadaşlar HTML-Kodu:
-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -
MySQL Version 4.1.22-standard i686
Uptime = 9 days 8 hrs 18 min 37 sec
Avg. qps = 0
Total Questions = 323246597
Threads Connected = 16
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 1474 out of 323246610 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 = 256
Current threads_cached = 103
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine
MAX CONNECTIONS
Current max_connections = 500
Current threads_connected = 15
Historic max_used_connections = 118
The number of used connections is 23% of the configured maximum.
Your max_connections variable seems to be fine.
MEMORY USAGE
Max Memory Ever Allocated : 842 M
Configured Max Per-thread Buffers : 2 G
Configured Max Global Buffers : 202 M
Configured Max Memory Limit : 2 G
Physical Memory : 1.97 G
Max memory limit exceeds 90% of physical memory
KEY BUFFER
Current MyISAM index space = 119 M
Current key_buffer_size = 64 M
Key cache miss rate is 1 : 19065
Key buffer fill ratio = 76.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 = 128 M
Current query_cache_used = 82 M
Current query_cache_limit = 1 M
Current Query cache Memory fill ratio = 64.26 %
Current query_cache_min_res_unit = 4 K
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 163 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 = 8702 files
The open_files_limit should typically be set to at least 2x-3x
that of table_cache if you have heavy MyISAM usage.
You currently have open more than 75% of your open_files_limit
You should set a higher value for open_files_limit in my.cnf
TABLE CACHE
Current table_cache value = 4096 tables
You have a total of 11247 tables
You have 4096 open tables.
Current table_cache hit rate is 12%, while 100% of your table ca
You should probably increase your table_cache
TEMP TABLES
Current max_heap_table_size = 16 M
Current tmp_table_size = 32 M
Of 252234 temp tables, 35% were created on disk
Effective in-memory tmp_table_size is limited to max_heap_table_
Perhaps you should increase your tmp_table_size and/or max_heap_
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 im
ratio of on disk temp tables.
TABLE SCANS
Current read_buffer_size = 1 M
Current table scan ratio = 53 : 1
read_buffer_size seems to be fine
TABLE LOCKING
Current Lock Wait ratio = 1 : 4085
You may benefit from selective use of InnoDB.
If you have long running SELECT's against MyISAM tables and perf
frequent updates consider setting 'low_priority_updates=1'
|
|
||||
|
Restorepkg yaptığım yedeklerde veritabanı çok yavaş yükleniyor..
Sebebi bu yaptığımız ayardan kaynaklanabilirmi ? ( post ) |
![]() |
LinkBacks (?)
LinkBack to this Thread: http://forum.iyinet.com/mysql-veritabani-sql/77047-tuning-primer-sh-mysql-tuning-scripti-mysql-performans-raporu.html
|
||||
| Konuyu Başlatan | For | Type | Tarih | |
| iyinet webmaster forumu 2008 seo yarışması 2008 Mayıs | This thread | Refback | 2008-07-12 04:39 | |
| iyinet webmaster forumu 2008 seo yarışması - iyinet webmaster forumu 2008 seo yarışması Mysql Performans Testi | This thread | Pingback | 2008-05-27 19:14 | |
| Turkwm.com: 5 dakikada hızlı mysql server optimizasyonu | This thread | Refback | 2008-05-15 16:20 | |
| Turkwm.com | This thread | Refback | 2008-05-15 13:42 | |
| 2007 Aralk -Webmaster Kaynak Sitesi | This thread | Refback | 2008-01-15 06:13 | |
| tuning-primer.sh mysql tuning scripti - Google - Webmaster Forum / Google Webmaster Fan | This thread | Refback | 2008-01-11 19:23 | |
| Mysql Tuning Scripti tuning-primer.sh | Webmaster Blogu | This thread | Pingback | 2007-12-23 21:44 | |
| Load sorunu yaşayanlar için genel tartışma konusu - vBulletin SEO Forums | This thread | Refback | 2007-12-12 10:58 | |
| Linux & Unix -Webmaster Kaynak Sitesi | This thread | Refback | 2007-12-11 08:55 | |
| mysql optimizastonu iin tuning-primer.sh scripti -Webmaster Kaynak Sitesi | This thread | Pingback | 2007-12-06 19:03 | |
| Seçenekler | |
| Stil | |
|
|
Benzer Konular
|
||||
| Konu | Konuyu Başlatan | Forum | Cevaplar | Son Mesaj |
| Tuning Merkezi | trebuchet55 | Yeni Site Tanıtımları | 0 | 2008-02-24 15:21 |
| Sanal Tuning | Alexis | Yeni Site Tanıtımları | 6 | 2008-01-18 04:07 |
| sadece tuning, sanal tuning siteleri ile - PR4 | Alexis | Google PR Link Değişimi | 0 | 2007-05-11 00:50 |
| Tuning Siteleri . Com | sverdlow | Yeni Site Tanıtımları | 2 | 2006-11-19 11:00 |
| Mysql Asp Performans Sorusu | disconnect | MySQL Veritabanı SQL | 6 | 2006-10-04 22:16 |