Pitu 160 Zgłoś post Napisano Październik 9, 2010 Witam Mógłby ktoś podpowiedzieć na podstawie mojego pliku my.cnf oraz wyniku z tuning-primer.sh co zmienić i na jakie wartości? Konfiguracja serwera System: CentOS Procesor: 2x2.33GHz Pamięć: 2GB my.cnf [mysqld] bind-address=127.0.0.1 datadir=/var/lib/mysql socket=/var/lib/mysql/mysql.sock query_cache_limit=1M query_cache_size=32M query_cache_type=1 max_connections=200 max_user_connections=600 interactive_timeout=100 wait_timeout=100 connect_timeout=10 thread_cache_size=128 key_buffer=128M join_buffer_size=2M max_allowed_packet=32M table_cache=2000 sort_buffer_size=2M read_buffer_size=2M read_rnd_buffer_size=1536K max_connect_errors=10 thread_concurrency=4 myisam_sort_buffer_size=64M skip-locking server-id=1 [mysql.server] user=mysql basedir=/var/lib [safe_mysqld] bind-address=127.0.0.1 err-log=/var/log/mysqld.log pid-file=/var/run/mysqld/mysqld.pid open_files_limit=8192 SAFE_MYSQLD_OPTIONS=”–defaults-file=/etc/my.cnf –log-slow-queries=/var/log/slow-queries.log” #[mysqldump] #quick #max_allowed_packet=16M [mysql] no-auto-rehash [isamchk] key_buffer=128M sort_buffer=128M read_buffer=32M write_buffer=32M [myisamchk] key_buffer=128M sort_buffer=128M read_buffer=32M write_buffer=32M [mysqlhotcopy] interactive-timeout Wynik z tuning-primer.sh -- MYSQL PERFORMANCE TUNING PRIMER -- - By: Matthew Montgomery - MySQL Version 5.0.77 i686 Uptime = 3 days 23 hrs 17 min 20 sec Avg. qps = 176 Total Questions = 60475231 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/5.0/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 sec. You have 760 out of 60475409 that take longer than 10 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.0/en/point-in-time-recovery.html WORKER THREADS Current thread_cache_size = 128 Current threads_cached = 123 Current threads_per_sec = 0 Historic threads_per_sec = 0 Your thread_cache_size is fine MAX CONNECTIONS Current max_connections = 200 Current threads_connected = 5 Historic max_used_connections = 161 The number of used connections is 80% of the configured maximum. Your max_connections variable seems to be fine. INNODB STATUS Current InnoDB index space = 8 M Current InnoDB data space = 5 M Current InnoDB buffer pool free = 0 % Current innodb_buffer_pool_size = 8 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 : 1.37 G Configured Max Per-thread Buffers : 1.50 G Configured Max Global Buffers : 170 M Configured Max Memory Limit : 1.66 G Physical Memory : 1.95 G Max memory limit seem to be within acceptable norms KEY BUFFER Current MyISAM index space = 264 M Current key_buffer_size = 128 M Key cache miss rate is 1 : 945 Key buffer free ratio = 76 % Your key_buffer_size seems to be fine 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.26 % Current query_cache_min_res_unit = 4 K However, 2779153 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 SORT OPERATIONS Current sort_buffer_size = 2 M Current read_rnd_buffer_size = 1 M Sort buffer seems to be fine JOINS Current join_buffer_size = 2.00 M You have had 3100 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 = 4210 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 2273 tables You have 2000 open tables. Current table_cache hit rate is 6% , 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 52292 temp tables, 27% 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 = 2 M Current table scan ratio = 194 : 1 read_buffer_size seems to be fine TABLE LOCKING Current Lock Wait ratio = 1 : 12819 Your table locking seems to be fine Udostępnij ten post Link to postu Udostępnij na innych stronach