Webmaster Forumu

Geri git   Webmaster Forumu > Webmaster Kaynak Eğitim Tanıtım Hizmet > MySQL Veritabanı SQL
Kayıt ol Blogs Yardım Üye Listesi Ajanda iTrader Forumları Okundu Kabul Et

MySQL Veritabanı SQL SQL MySQL Access MSSQL Oracle Veritabani Database

Cevapla Add This!
 
LinkBack (8) Seçenekler Stil
  #21 (permalink)   iTrader 
Alt 2007-12-02, 11:12
tr.st - ait Kullanıcı Resmi (Avatar)
nerd
 
Üyelik tarihi: Feb 2003
Nerden: Ordan, burdan..
Mesajlar: 2.290
Tecrübe Puanı: 7
iTrader: %100/8
tr.st has a spectacular aura abouttr.st has a spectacular aura abouttr.st has a spectacular aura about
Standart

bende aşağıdaki verilere göre yardım alabilir miyim? (fine olanları çıkardım listeden)

Alıntı:
SLOW QUERIES
Current long_query_time = 10 sec.
You have 237 out of 523173 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.



MAX CONNECTIONS
Current max_connections = 500
Current threads_connected = 1
Historic max_used_connections = 8
The number of used connections is 1% 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 : 101 M
Configured Max Per-thread Buffers : 2 G
Configured Max Global Buffers : 58 M
Configured Max Memory Limit : 2 G
Physical Memory : 978.82 M

Max memory limit exceeds 90% of physical memory

KEY BUFFER
Current MyISAM index space = 7 M
Current key_buffer_size = 16 M
Key cache miss rate is 1 : 623
Key buffer fill ratio = 34.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 = 26 M
Current query_cache_limit = 1 M
Current Query cache Memory fill ratio = 81.34 %
Current query_cache_min_res_unit = 4 K
Query Cache is 5 % 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.
However, 3657 queries have been removed from the query cache due to lack of memory
Perhaps you should raise query_cache_size
MySQL won't cache query results that are larger than query_cache_limit in size



JOINS
Current join_buffer_size = 1.00 M
You have had 80 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.


TEMP TABLES
Current max_heap_table_size = 16 M
Current tmp_table_size = 32 M
Of 10314 temp tables, 83% 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.
__________________
Word Press Temalar
Alıntı ile Cevapla

  #22 (permalink)   iTrader 
Alt 2007-12-02, 14:37
mami
 
Üyelik tarihi: Sep 2006
Nerden: dreamcity
Mesajlar: 4.330
Blog Entries: 3
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

yanlış bişey yapmamak adına, bende rica edebilirmiyim
teşekkürler
Alıntı:
-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -

MySQL Version 5.0.27 i686

Uptime = 18 days 1 hrs 5 min 41 sec
Avg. qps = 39
Total Questions = 61695504
Threads Connected = 2

Server has been running for over 48hrs.
It should be safe to follow these recommendations




SLOW QUERIES
Current long_query_time = 10 sec.
You have 1481 out of 61695552 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 = 64
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 = 2
Historic max_used_connections = 66
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

MEMORY USAGE
Max Memory Ever Allocated : 396 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 = 4 M
Current key_buffer_size = 128 M
Key cache miss rate is 1 : 297206
Key buffer fill ratio = 1.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 = 9 M
Current query_cache_limit = 1 M
Current Query cache Memory fill ratio = 30.72 %
Current query_cache_min_res_unit = 4 K
Query Cache is 14 % 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 1536 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 298 tables
You have 379 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 253607 temp tables, 66% 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 = 539 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 1 : 232
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'
If you have a high concurrency of inserts on Dynamic row-length tables
consider setting 'concurrent_insert=2'.
Alıntı ile Cevapla

  #23 (permalink)   iTrader 
Alt 2007-12-02, 15:49
iyinet - ait Kullanıcı Resmi (Avatar)
Paylaşım için teşekkürler
 
Üyelik tarihi: Sep 2002
Mesajlar: 6.055
Blog Entries: 2
Tecrübe Puanı: 3
iTrader: %100/6
iyinet is just really niceiyinet is just really niceiyinet is just really niceiyinet is just really nice
Standart

Alıntı:
i.ari´isimli üyeden Alıntı Mesajı göster
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/...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'
i.ari, 2. sunucu için 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 = 1800
low_priority_updates = 1
__________________
Forum Reklam Site Reklam
Alıntı ile Cevapla

  #24 (permalink)   iTrader 
Alt 2007-12-02, 15:52
iyinet - ait Kullanıcı Resmi (Avatar)
Paylaşım için teşekkürler
 
Üyelik tarihi: Sep 2002
Mesajlar: 6.055
Blog Entries: 2
Tecrübe Puanı: 3
iTrader: %100/6
iyinet is just really niceiyinet is just really niceiyinet is just really niceiyinet is just really nice
Standart

Alıntı:
tr.st´isimli üyeden Alıntı Mesajı göster
bende aşağıdaki verilere göre yardım alabilir miyim? (fine olanları çıkardım listeden)
Tüm çıktıya bakmam lazım en baştan itibaren.
__________________
Forum Reklam Site Reklam
Alıntı ile Cevapla

  #25 (permalink)   iTrader 
Alt 2007-12-02, 15:58
iyinet - ait Kullanıcı Resmi (Avatar)
Paylaşım için teşekkürler
 
Üyelik tarihi: Sep 2002
Mesajlar: 6.055
Blog Entries: 2
Tecrübe Puanı: 3
iTrader: %100/6
iyinet is just really niceiyinet is just really niceiyinet is just really niceiyinet is just really nice
Standart

Alıntı:
Mywedding´isimli üyeden Alıntı Mesajı göster
yanlış bişey yapmamak adına, bende rica edebilirmiyim
teşekkürler
Index boyutun çok ufak, uygulaman vbulletin gibi hazır kod ise sorun yok ama kendi kodlamanız ise grekli index lerin yaratılıp yaratılmadığını bir inceleyin.

thread_cache_size = 384
max_connections = 200
key_buffer = 32M
query_cache_limit = 4M
table_cache = 500
low_priority_updates = 1
__________________
Forum Reklam Site Reklam
Alıntı ile Cevapla

  #26 (permalink)   iTrader 
Alt 2007-12-04, 00:42
Member
 
Üyelik tarihi: Sep 2006
Mesajlar: 340
Tecrübe Puanı: 2
iTrader: %100/3
ENVER is an unknown quantity at this point
Standart

Bende yardım alabilir miyim rica etsem.
Alıntı:
-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -

MySQL Version 4.1.22-standard i686

Uptime = 2 days 11 hrs 2 min 3 sec
Avg. qps = 85
Total Questions = 18204090
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/...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 6 out of 18204107 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 = 182
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 = 1
Historic max_used_connections = 184
The number of used connections is 36% 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 : 4 G
Configured Max Global Buffers : 266 M
Configured Max Memory Limit : 4 G
Physical Memory : 3.95 G

Max memory limit exceeds 90% of physical memory

KEY BUFFER
Current MyISAM index space = 537 M
Current key_buffer_size = 128 M
Key cache miss rate is 1 : 107687
Key buffer fill ratio = 99.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 = 128 M
Current query_cache_used = 72 M
Current query_cache_limit = 8 M
Current Query cache Memory fill ratio = 56.90 %
Current query_cache_min_res_unit = 4 K
Query Cache is 20 % 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 = 4 M
Current record/read_rnd_buffer_size = 764 K
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 2.00 M
You have had 568 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 = 4510 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 = 2000 tables
You have a total of 1042 tables
You have 1531 open tables.
The table_cache value seems to be fine

TEMP TABLES
Current max_heap_table_size = 127 M
Current tmp_table_size = 128 M
Of 517889 temp tables, 1% 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 = 446 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 1 : 267
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'
Alıntı ile Cevapla

  #27 (permalink)   iTrader 
Alt 2007-12-04, 05:18
iyinet - ait Kullanıcı Resmi (Avatar)
Paylaşım için teşekkürler
 
Üyelik tarihi: Sep 2002
Mesajlar: 6.055
Blog Entries: 2
Tecrübe Puanı: 3
iTrader: %100/6
iyinet is just really niceiyinet is just really niceiyinet is just really niceiyinet is just really nice
Standart

Alıntı:
ENVER´isimli üyeden Alıntı Mesajı göster
Bende yardım alabilir miyim rica etsem.
Makinanin ozelliklerini yazmamissin.
2Gb oldugunu varsayiyorum:

Degerleri bu sekilde degistirip 3-4 gun sonra scripti yine calistir sonuclari karsilastiralim. 2 gun aslinda az bir sure.

max_connections = 200
key_buffer = 256M
query_cache_size = 40M
query_cache_limit = 4M
low_priority_updates = 1
__________________
Forum Reklam Site Reklam
Alıntı ile Cevapla

  #28 (permalink)   iTrader 
Alt 2007-12-04, 13:51
Member
 
Üyelik tarihi: Sep 2006
Mesajlar: 340
Tecrübe Puanı: 2
iTrader: %100/3
ENVER is an unknown quantity at this point
Standart

kusura bakma yazmamışım makinada 4gb ram var işlemci olarakta 4X Name: Intel(R) Xeon(R) CPU 5160 @ 3.00GHz kullanıyor
Alıntı:
iyinet´isimli üyeden Alıntı Mesajı göster
Makinanin ozelliklerini yazmamissin.
2Gb oldugunu varsayiyorum:

Degerleri bu sekilde degistirip 3-4 gun sonra scripti yine calistir sonuclari karsilastiralim. 2 gun aslinda az bir sure.

max_connections = 200
key_buffer = 256M
query_cache_size = 40M
query_cache_limit = 4M
low_priority_updates = 1
Alıntı ile Cevapla

  #29 (permalink)   iTrader 
Alt 2007-12-04, 15:38
Member
 
Üyelik tarihi: May 2007
Mesajlar: 277
Tecrübe Puanı: 1
iTrader: %0/0
Remark is on a distinguished road
Standart

bende de bu sonuç çıktı..
neler yapmam gerekiyor yardımcı olursanız çok sevinirim sayın iyinet

Teşekkürler


floodkoruma-2.0-1.c5x.i386.rpm pure-ftpd-1.0.21
httpbanla.sh pure-ftpd-1.0.21.tar.gz
mysqlauth.A18102 tuning-primer.sh
proftpd-1.3.0a x
proftpd-1.3.0a.tar.gz ZendOptimizer-3.2.2-linux-glibc21-i386
psa ZendOptimizer-3.2.2-linux-glibc21-i386.tar.gz
pure-ftpd-1.0.14-1.i386.rpm
[root@server ~]# ./tuning-primer.sh
-bash: ./tuning-primer.sh: Permission denied
[root@server ~]# chmod u+x tuning-primer.sh
[root@server ~]# ./tuning-primer.sh

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

MySQL Version 4.1.20 i686

Uptime = 3 days 23 hrs 6 min 38 sec
Avg. qps = 49
Total Questions = 16891734
Threads Connected = 3

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 380 out of 16891746 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 = 23
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 = 3
Historic max_used_connections = 26
The number of used connections is 5% 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 : 423 M
Configured Max Per-thread Buffers : 2 G
Configured Max Global Buffers : 282 M
Configured Max Memory Limit : 2 G
Physical Memory : 946.83 M

Max memory limit exceeds 90% of physical memory

KEY BUFFER
Current MyISAM index space = 89 M
Current key_buffer_size = 16 M
Key cache miss rate is 1 : 765
Key buffer fill ratio = 60.00 %
Your key_buffer_size seems to be fine

QUERY CACHE
Query cache is enabled
Current query_cache_size = 256 M
Current query_cache_used = 173 M
Current query_cache_limit = 8 M
Current Query cache Memory fill ratio = 67.79 %
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 = 256 K
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 1.00 M
You have had 13565 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 = 2558 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 2369 tables
You have 1024 open tables.
Current table_cache hit rate is 9%, 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 268173 temp tables, 35% 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 = 1 M
Current table scan ratio = 2053 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 1 : 23714
Your table locking seems to be fine
Alıntı ile Cevapla

  #30 (permalink)   iTrader 
Alt 2007-12-04, 16:45
iyinet - ait Kullanıcı Resmi (Avatar)
Paylaşım için teşekkürler
 
Üyelik tarihi: Sep 2002
Mesajlar: 6.055
Blog Entries: 2
Tecrübe Puanı: 3
iTrader: %100/6
iyinet is just really niceiyinet is just really niceiyinet is just really niceiyinet is just really nice
Standart

Alıntı:
Remark´isimli üyeden Alıntı Mesajı göster
bende de bu sonuç çıktı..
neler yapmam gerekiyor yardımcı olursanız çok sevinirim sayın iyinet

Teşekkürler


floodkoruma-2.0-1.c5x.i386.rpm pure-ftpd-1.0.21
httpbanla.sh pure-ftpd-1.0.21.tar.gz
mysqlauth.A18102 tuning-primer.sh
proftpd-1.3.0a x
proftpd-1.3.0a.tar.gz ZendOptimizer-3.2.2-linux-glibc21-i386
psa ZendOptimizer-3.2.2-linux-glibc21-i386.tar.gz
pure-ftpd-1.0.14-1.i386.rpm
[root@server ~]# ./tuning-primer.sh
-bash: ./tuning-primer.sh: Permission denied
[root@server ~]# chmod u+x tuning-primer.sh
[root@server ~]# ./tuning-primer.sh

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

MySQL Version 4.1.20 i686

Uptime = 3 days 23 hrs 6 min 38 sec
Avg. qps = 49
Total Questions = 16891734
Threads Connected = 3

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 380 out of 16891746 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 = 23
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 = 3
Historic max_used_connections = 26
The number of used connections is 5% 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 : 423 M
Configured Max Per-thread Buffers : 2 G
Configured Max Global Buffers : 282 M
Configured Max Memory Limit : 2 G
Physical Memory : 946.83 M

Max memory limit exceeds 90% of physical memory

KEY BUFFER
Current MyISAM index space = 89 M
Current key_buffer_size = 16 M
Key cache miss rate is 1 : 765
Key buffer fill ratio = 60.00 %
Your key_buffer_size seems to be fine

QUERY CACHE
Query cache is enabled
Current query_cache_size = 256 M
Current query_cache_used = 173 M
Current query_cache_limit = 8 M
Current Query cache Memory fill ratio = 67.79 %
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 = 256 K
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 1.00 M
You have had 13565 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 = 2558 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 2369 tables
You have 1024 open tables.
Current table_cache hit rate is 9%, 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 268173 temp tables, 35% 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 = 1 M
Current table scan ratio = 2053 : 1
read_buffer_size seems to be fine

TABLE LOCKING
Current Lock Wait ratio = 1 : 23714
Your table locking seems to be fine
Degerleri bu sekilde degistirip yoksa ekleyip 3-4 gun sonra scripti yine calistirin sonuclari karsilastiralim.

thread_cache_size = 384
max_connections = 200
key_buffer = 128M
query_cache_size = 64M
query_cache_limit = 4M
table_cache = 2500
low_priority_updates = 1
__________________
Forum Reklam Site Reklam
Alıntı ile Cevapla

Cevapla


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
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

Konuyu Toplam 1 Üye okuyor. (0 Kayıtlı üye ve 1 Misafir)
 
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


Bütün Zaman Ayarları WEZ +2 olarak düzenlenmiştir. Şu Anki Saat: 17:46 .


Powered by vBulletin® Version 3.6.10
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO 3.1.0

Firefox