MySQL Server bei zu vielen Verbindungen nicht mehr erreichbar.

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

MySQL Version 5.0.51a-24+lenny1 x86_64

Uptime = 78 days 23 hrs 59 min 28 sec
Avg. qps = 37
Total Questions = 254649395
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/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 1907 out of 254649423 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 http://dev.mysql.com/doc/refman/5.0/en/point-in-time-recovery.html

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

MAX CONNECTIONS
Current max_connections = 100
Current threads_connected = 3
Historic max_used_connections = 101
The number of used connections is 101% of the configured maximum.
You should raise max_connections

MEMORY USAGE
Max Memory Ever Allocated : 307 M
Configured Max Per-thread Buffers : 262 M
Configured Max Global Buffers : 42 M
Configured Max Memory Limit : 304 M
Physical Memory : 11.75 G
Max memory limit seem to be within acceptable norms

KEY BUFFER
Current MyISAM index space = 64 M
Current key_buffer_size = 16 M
Key cache miss rate is 1 : 214
Key buffer free ratio = 66 %
Your key_buffer_size seems to be fine

QUERY CACHE
Query cache is enabled
Current query_cache_size = 16 M
Current query_cache_used = 12 M
Current query_cache_limit = 1 M
Current Query cache Memory fill ratio = 75.03 %
Current query_cache_min_res_unit = 4 K
Query Cache is 24 % 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 read_rnd_buffer_size = 256 K
Sort buffer seems to be fine

JOINS
Current join_buffer_size = 132.00 K
You have had 3401886 queries where a join could not use an index properly
You have had 77 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 = 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 309 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 8776595 temp tables, 14% 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 = 42984 : 1
You have a high ratio of sequential access requests to SELECTs
You may benefit from raising read_buffer_size and/or improving your use of indexes.

TABLE LOCKING
Current Lock Wait ratio = 1 : 41
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'.

max_connections 500

Aber der Test oben zeigt ja angeblich nur 100 an :confused:
 
Die Max-Connections kannst Du einfach erhöhen. Die richtige my.cf nehmen und den Wert in die passenden Sektion ("mysqld") schreiben. Ein MySQL-Neustart braucht es dann zusätzlich.

Dazu die üblichen Verdächtigen, die das Script ja auch schön rot bemängelt:
- table_cache (sollte bei der aktuellen Tabellen-Anzahl auf 400 oder höher gesetzt werden)
- open_files_limit (ca. 3 * table_cache)

huschi.
 
Hi,

habe nun alles eingestellt, danke. Habe jetzt aber folgendes festgestellt: Anscheinend kommt man immer um 20 nach bis um halb, also 10 Minuten zu jeder Stunde nur mit minutenlanger Verzögerung ins Kontrollzentrum oder in die Privaten Nachrichten. Der Rest funktioniert?

Sehr komisch oder? :confused:
 
Wenn es so regelmäßig ist, dann tippe ich mal auf einen Cronjob der einen Table-Lock setzt.

huschi.
 
Gerade einen ausgeschaltet der stündlich lief, jedoch beseitigte dies nicht das Problem. Könnte es an was anderem liegen?
 
Du sitzt wirklich an diesem Server. Daher bist Du der Einzige der diese Frage wirklich beantworten kann. Wir können nur raten.
Mithilfe von "show processlist;" könnte man in der fraglichen Zeit dem Täter auf die Spur kommen.

huschi.
 
Back
Top