• 29-09-2008, 04:15:12
    #28
    bu scripti sunucuna indir ve kur 48saat sonra çıktı al buraya ekle, sağlıklı sonucu ancak böyle alabiliriz..

    aslında işlemleri yap, bir çıktı al, posta ekle, bir bakalım..

    ama yazdığım gibi, en sağlıklı ayar için, scripti kurup 48saat sonra alacağın rapor, daha iyi olur..

    indir..
    wget http://day32.com/MySQL/tuning-primer.sh
    izinleri ver
    chmod u+x tuning-primer.sh
    çalıştır ve çıktısını al..
    ./tuning-primer.sh

    http://www.day32.com/MySQL/
  • 06-10-2008, 03:03:57
    #29
    Üyeliği durduruldu
    mysqld is alive

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

    MySQL Version 4.1.20 i686

    Uptime = 16 days 14 hrs 47 min 6 sec
    Avg. qps = 13
    Total Questions = 19789967
    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:
    MySQL :: MySQL 3.23, 4.0, 4.1 Reference Manual :: 5.1.3 System Variables
    Visit MySQL :: MySQL Enterprise Advisors
    for info about MySQL's Enterprise Monitoring and Advisory Service

    SLOW QUERIES
    The slow query log is NOT enabled.
    Current long_query_time = 10 sec.
    You have 347 out of 19789981 that take longer than 10 sec. to complete
    Your long_query_time may be too high, I typically set this under 5 sec.

    BINARY UPDATE LOG
    The binary update log is NOT enabled.
    You will not be able to do point in time recovery
    See MySQL :: MySQL 3.23, 4.0, 4.1 Reference Manual :: 6.3 Point-in-Time Recovery

    WORKER THREADS
    Current thread_cache_size = 0
    Current threads_cached = 0
    Current threads_per_sec = 1
    Historic threads_per_sec = 0
    Your thread_cache_size is fine

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

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

    KEY BUFFER
    Current MyISAM index space = 839 M
    Current key_buffer_size = 7 M
    Key cache miss rate is 1 : 22
    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 read_rnd_buffer_size = 256 K
    Sort buffer seems to be fine

    JOINS
    Current join_buffer_size = 132.00 K
    You have had 1235 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 = 1024 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 1888 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 149756 temp tables, 24% 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 = 1023 : 1
    read_buffer_size seems to be fine

    TABLE LOCKING
    Current Lock Wait ratio = 1 : 3136
    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'
  • 23-02-2009, 00:03:53
    #30
    CPU: GenuineIntel, Intel(R) Xeon(R)CPU X3210 @ 2.13GHz
    RAM: 2048 MB
    Sayfa Gösterimi: 80k
    Ortalama load average: 4.16, 2.95, 2.26
    MySql Sürekli 99.9 cpu kullanıyor. günde 2-3 defa donuyor.
    sistem: centos plesk 9.0.1 kurulu.
    trafik 100 Mbit sınırsız.
    Sizce Nasıl bir yapılandırma yapmam gerekli.