Denn der "Ausfall" heute um 12:00 war deutlich kürzer als 30 Sekunden und damit kaum zu bemerken!
![Very Happy :D](./images/smilies/icon_biggrin.gif)
Gruß,
Daniel
Code: Alles auswählen
leela:~# ./tuning-primer.sh
- INITIAL LOGIN ATTEMPT FAILED -
Testing Stored for passwords: None Found
- RETRY LOGIN ATTEMPT FAILED -
Could not auto detect login info!
Do you have your login handy ? [y/N] : y
User: xxxxxxxxxxxxxxx
Password:
Would you like me to create a ~/.my.cnf file for you? [y/N] :
-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -
MySQL Version 5.0.32-Debian_7etch5-log x86_64
Uptime = 2 days 11 hrs 38 min 32 sec
Avg. qps = 8
Total Questions = 1894589
Threads Connected = 18
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 = 5 sec.
You have 227 out of 1894610 that take longer than 5 sec. to complete
Your long_query_time seems to be fine
BINARY UPDATE LOG
The binary update log is enabled
WORKER THREADS
Current thread_cache_size = 8
Current threads_cached = 0
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine
MAX CONNECTIONS
Current max_connections = 350
Current threads_connected = 19
Historic max_used_connections = 57
The number of used connections is 16% 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 : 5 G
Configured Max Global Buffers : 170 M
Configured Max Memory Limit : 5 G
Physical Memory : 1.96 G
Max memory limit exceeds 90% of physical memory
KEY BUFFER
Current MyISAM index space = 551 M
Current key_buffer_size = 128 M
Key cache miss rate is 1 : 29
Key buffer fill ratio = 52.00 %
Your key_buffer_size seems to be fine
QUERY CACHE
Query cache is enabled
Current query_cache_size = 32 M
Current query_cache_used = 16 M
Current query_cache_limit = 1 M
Current Query cache Memory fill ratio = 51.49 %
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 = 128.00 K
You have had 21 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 = 3432 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 = 1536 tables
You have a total of 182 tables
You have 281 open tables.
The table_cache value seems to be fine
TEMP TABLES
Current max_heap_table_size = 16 M
Current tmp_table_size = 96 M
Of 43526 temp tables, 6% 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 = 69 : 1
read_buffer_size seems to be fine
TABLE LOCKING
Current Lock Wait ratio = 1 : 487
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'.
leela:~#
Ich habe mich schon erfolgreich dieser Faustregel bedient:feltel hat geschrieben:Die Max-Connections werde ich noch weiter runterschrauben.
Code: Alles auswählen
max_connections = max_clients / 2
Der Rest des Boards funktioniert einwandfrei.Allgemeiner Fehler
SQL ERROR [ mysql4 ]
Got error 134 from storage engine [1030]
Das Problem habe ich auch.ub13 hat geschrieben:Kann es sein, das das Forum seit 2-3 Tagen wieder hakelt? oder ist das nur bei mir so?
Auf dem Server läuft auch ein jabberd, ein daemon für das jabber-Protokoll (ähnlich icq). Und damit die jabber-User auch Kontakt zu icq-Usern haben können, wird der icq-transport eingesetzt, vereinfacht gesagt wie ein gateway zwischen den beiden Systemen.Milbret hat geschrieben: Aber wozu macht man über einen Server was mit ICQ und dann Transport?
Das ist aber eine eklige Lösung.Ich hab auch einen Webserver von S4Y mit Etch und hab dort auch ein doofes Serverproblem.
Apache spinnt dort irgendwie und mein Kollege lässt ihn per Script alle 200 Sekunden neustarten.
Ist zwar keine schöne Lösung aber das läuft so schnell, da merkt man nicht viel vom neustart![]()