SMF Support > Server Performance and Configuration
README: Checklist for performance problems
villasg:
Hello can help me ?
MySQL Statistics
MySQL 5.0.x
--- Code: ---Connections per second: 1.6509
Kilobytes received per second: 6.5836
Kilobytes sent per second: 0.3797
Queries per second: 45.8007
Percentage of slow queries: 0
Opened vs. Open tables:
(table_cache) 54633.9844 (should be <= 80)
Table cache usage:
(table_cache) 1 (should be >= 0.5 and <= 0.9)
Key buffer read hit rate:
(key_buffer_size) 0.0361 (should be <= 0.01)
Key buffer write hit rate:
(key_buffer_size) 0.2215 (should be <= 0.5)
Thread cache hit rate:
(thread_cache_size) 1 (should be >= 30 )
Thread cache usage:
(thread_cache_size) 0 (should be >= 0.7 and <= 0.9)
Temporary table disk usage:
(tmp_table_size) 0.2927 (should be <= 0.5)
Sort merge pass rate:
(sort_buffer) 0 (should be <= 0.001)
Query cache enabled:
(query_cache_type) 1 (should be >= 1 and <= 1)
Query cache miss rate:
(query_cache_limit) 1 (should be <= 0.5)
Query cache prune rate:
(query_cache_size) 0 (should be <= 0.05)
--- End code ---
Have this abnormal .
How can i fix ?
Opened vs. Open tables:
(table_cache) 54632.0625 (should be <= 80)
Table cache usage:
(table_cache) 1 (should be >= 0.5 and <= 0.9)
Key buffer read hit rate:
(key_buffer_size) 0.0361 (should be <= 0.01)
Thread cache hit rate:
(thread_cache_size) 1 (should be >= 30 )
Thread cache usage:
(thread_cache_size) 0 (should be >= 0.7 and <= 0.9)
Query cache miss rate:
(query_cache_limit) 1 (should be <= 0.5)
metallica48423:
All -- please start new topics in this board for your support issue -- thanks!
This topic is purely informational
fractalbit:
Hello all. Status.php is great tool. Thanks to this we spotted a query that would bring the whole server down in a matter of seconds! Every time we executed this query through phpmyadmin it would bring the server down. But we spotted this query by luck, because on of the admins saw the query in status.php that it had locked out all other queries.
So my question is: Can status.php be modified so that it logs (on a table or txt file) the queries that take more than X seconds to execute, or the queries that lock others out for more than X seconds? So we will not rely on chance anymore and easily find the problematic queries? Of course as i undestand it, status.php should be made as a cron job to run every second or so? Whould this have a large impact on server performance?
Thanks for your time
Mark Rose:
MySQL has this feature built in. See: http://dev.mysql.com/doc/refman/5.0/en/slow-query-log.html
I'd recommend using this tool to analyse the slow query log: http://www.mysqlperformanceblog.com/files/utils/mysql_slow_log_parser (save it, run "chmod a+x" to make it executable).
If you're running into queries that are blocking other queries, it's one of two things:
1. You're running an ALTER TABLE (such as in phpMyAdmin).
2. You're running MyISAM and you're suffering from write-locks (convert the table to InnoDB).
SergeantAsh:
I just fired up your status.php script, and I'm getting this...
Opened vs. Open tables:
(table_cache) 34138.78 (should be <= 80)
In figures, this looks bad!! Is it? I'm on a Dreamhost PS Server.
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version