Hallo,
bei meinem dedizierten Server läuft MySQL fast immer mit über 95% Auslastung (laut Webmin). Besonders abends ist die Seite spürbar langsam.
tuning-primer.sh liefert mir folgende Ausgabe:
Was könnte ich in der my.conf verbessern?
Es handelt sich um ein Debian Lenny System mit 6 GB RAM und Q8300 @ 2.50GHz CPU, falls das relevant ist
Vielen Dank
bei meinem dedizierten Server läuft MySQL fast immer mit über 95% Auslastung (laut Webmin). Besonders abends ist die Seite spürbar langsam.
tuning-primer.sh liefert mir folgende Ausgabe:
Code:
MySQL Version 5.0.51a-24+lenny5-log x86_64
Uptime = 7 days 14 hrs 18 min 27 sec
Avg. qps = 467
Total Questions = 306615841
Threads Connected = 5
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:
[url]http://dev.mysql.com/doc/refman/5.0/en/server-system-variables.html[/url]
Visit [url]http://www.mysql.com/products/enterprise/advisors.html[/url]
for info about MySQL's Enterprise Monitoring and Advisory Service
SLOW QUERIES
The slow query log is enabled.
Current long_query_time = 4 sec.
You have 4217 out of 306615960 that take longer than 4 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 [url]http://dev.mysql.com/doc/refman/5.0/en/point-in-time-recovery.html[/url]
WORKER THREADS
Current thread_cache_size = 16
Current threads_cached = 11
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine
MAX CONNECTIONS
Current max_connections = 250
Current threads_connected = 5
Historic max_used_connections = 215
The number of used connections is 86% of the configured maximum.
You should raise max_connections
INNODB STATUS
Current InnoDB index space = 0 bytes
Current InnoDB data space = 0 bytes
Current InnoDB buffer pool free = 95 %
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 : 4.00 G
Configured Max Per-thread Buffers : 4.05 G
Configured Max Global Buffers : 524 M
Configured Max Memory Limit : 4.57 G
Physical Memory : 5.84 G
Max memory limit seem to be within acceptable norms
KEY BUFFER
Current MyISAM index space = 50 M
Current key_buffer_size = 512 M
Key cache miss rate is 1 : 2784
Key buffer free ratio = 80 %
Your key_buffer_size seems to be fine
QUERY CACHE
Query cache is enabled
Current query_cache_size = 2 M
Current query_cache_used = 545 K
Current query_cache_limit = 1 M
Current Query cache Memory fill ratio = 26.61 %
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 = 16 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 22215 queries where a join could not use an index properly
You have had 333754 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 = 2308 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 330 tables
You have 406 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 4477271 temp tables, 38% 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 = 1720 : 1
read_buffer_size seems to be fine
TABLE LOCKING
Current Lock Wait ratio = 1 : 137
You may benefit from selective use of InnoDB.Was könnte ich in der my.conf verbessern?
Es handelt sich um ein Debian Lenny System mit 6 GB RAM und Q8300 @ 2.50GHz CPU, falls das relevant ist
Vielen Dank
Last edited by a moderator:
