ich stehe derzeit vor einem sehr großem Problem. Auf meinem Rootserver herscht derzeit eine recht unübersichtliche Last an dem mysql-server. Ich habe schon mehrfache Konfigurationen ausprobiert, leider brachte mich keine davon zu einem angemessenem Erfolg.
-- MYSQL PERFORMANCE TUNING PRIMER --
- By: Matthew Montgomery -
MySQL Version 5.0.32-Debian_7etch5 x86_64
Uptime = 0 days 21 hrs 19 min 23 sec
Avg. qps = 35
Total Questions = 2690598
Threads Connected = 714
Warning: Server has not been running for at least 48hrs.
It may not be safe to use 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 43 out of 2690619 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 = 6
Current threads_per_sec = 0
Historic threads_per_sec = 0
Your thread_cache_size is fine
MAX CONNECTIONS
Current max_connections = 2500
Current threads_connected = 714
Historic max_used_connections = 720
The number of used connections is 28% of the configured maximum.
Your max_connections variable seems to be fine.
MEMORY USAGE
Max Memory Ever Allocated : 11 G
Configured Max Per-thread Buffers : 38 G
Configured Max Global Buffers : 151 M
Configured Max Memory Limit : 38 G
Physical Memory : 3.84 G
Max memory limit exceeds 90% of physical memory
KEY BUFFER
Current MyISAM index space = 16 M
Current key_buffer_size = 125 M
Key cache miss rate is 1 : 1705
Key buffer fill ratio = 6.00 %
Your key_buffer_size seems to be too high.
Perhaps you can use these resources elsewhere
QUERY CACHE
Query cache is enabled
Current query_cache_size = 16 M
Current query_cache_used = 5 M
Current query_cache_limit = 1 M
Current Query cache Memory fill ratio = 36.20 %
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 = 15 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 1 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 = 65535 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 = 31512 tables
You have a total of 180 tables
You have 374 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 14585 temp tables, 1% 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 = 16388 : 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 : 11
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'.
„If there’s more than one possible outcome of a job or task, and one
of those outcomes will result in disaster or an undesirable consequence,
then somebody will do it that way.“ -- Edward Aloysius Murphy Jr.
MEMORY USAGE
Max Memory Ever Allocated : 1 G
Configured Max Per-thread Buffers : 14 G
Configured Max Global Buffers : 1 G
Configured Max Memory Limit : 16 G
Physical Memory : 3.84 G
Max memory limit exceeds 90% of physical memory
Sintec wrote:So die Slow-Queries habe ich gestern Abend noch aktiviert. Verstehe ich richtig das jede Abfrage die in der Log steht überarbeitet werden muss?
Du kannst das vorher mit "mysqldumpslow" ein wenig ordnen lassen.
leider muss ich feststellen das seit der neuen Konfiguration einige php-scripts an Ihren Aufgaben scheitern. Das merkwürdige ist, dass wenn ich das Script mehrfach versuche auszuführen, dass es dann irgendwann klappt und er eine Verbindung zur Datenbank aufbauen kann.
Sofern das Script abbricht erscheint folgende Fehlermeldung:
Warning: mysql_connect(): Lost connection to MySQL server at 'reading authorization packet', system error: 0 in /home/uploadengine/last .php on line 3
Warning: mysql_select_db(): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) in /home/uploadengine/ last.php on line 4
Warning: mysql_select_db(): A link to the server could not be established in /home/uploadengine/last.php on line 4
Warning: mysql_query(): Can't connect to local MySQL server through socket '/var/run/mysqld/mysqld.sock' (2) in /home/uploadengine/last .php on line 8
Ich hoffe Ihr habt eine Idee wie ich diesen Fehler beheben kann.
Count: 7 Time=0.00s (0s) Lock=0.00s (0s) Rows=2.6 (18), xlspread[xlspread]@localhost
SELECT `group_id` FROM `user_group` WHERE `user_id`='S'
Count: 2 Time=0.00s (0s) Lock=0.00s (0s) Rows=1.0 (2), xlspread[xlspread]@localhost
SELECT id FROM users WHERE login = 'S'
geloggt werden auch alle queries die keinen Index benutzen (log_queries_not_using_indexes). Es ist also zu prüfen ob ein Index auf user_id in der user_group und auf login in der users gesetzt werden muss / sollte.
