1
Discussion & Troubleshooting / Re: My site is down, help please!
« on: April 14, 2009, 05:29:34 PM »
By the way, I have these red information on my database Runtime Information: (I'm not a database expert, that's why I'll almost don't understand anything...)
Slow_queries 644 The number of queries that have taken more than long_query_time seconds.Documentation
Innodb_buffer_pool_reads 2,549 The number of logical reads that InnoDB could not satisfy from buffer pool and had to do a single-page read.
Innodb_log_waits 1 The number of waits we had because log buffer was too small and we had to wait for it to be flushed before continuing.
Innodb_row_lock_time_avg 18 The average time to acquire a row lock, in milliseconds.
Innodb_row_lock_waits 3 The number of times a row lock had to be waited for.
Handler_read_rnd 1,699 M The number of requests to read a row based on a fixed position. This is high if you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan whole tables or you have joins that don't use keys properly.
Handler_read_rnd_next 1,029 M The number of requests to read the next row in the data file. This is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have.
Created_tmp_disk_tables 880 k The number of temporary tables on disk created automatically by the server while executing statements. If Created_tmp_disk_tables is big, you may want to increase the tmp_table_size value to cause temporary tables to be memory-based instead of disk-based.
Select_full_join 107 k The number of joins that do not use indexes. If this value is not 0, you should carefully check the indexes of your tables.
Sort_merge_passes 3 The number of merge passes the sort algorithm has had to do. If this value is large, you should consider increasing the value of the sort_buffer_size system variable.
Opened_tables 74 k The number of tables that have been opened. If opened tables is big, your table cache value is probably too small.
Table_locks_waited 53 k The number of times that a table lock could not be acquired immediately and a wait was needed. If this is high, and you have performance problems, you should first optimize your queries, and then either split your table or tables or use replication.
Slow_queries 644 The number of queries that have taken more than long_query_time seconds.Documentation
Innodb_buffer_pool_reads 2,549 The number of logical reads that InnoDB could not satisfy from buffer pool and had to do a single-page read.
Innodb_log_waits 1 The number of waits we had because log buffer was too small and we had to wait for it to be flushed before continuing.
Innodb_row_lock_time_avg 18 The average time to acquire a row lock, in milliseconds.
Innodb_row_lock_waits 3 The number of times a row lock had to be waited for.
Handler_read_rnd 1,699 M The number of requests to read a row based on a fixed position. This is high if you are doing a lot of queries that require sorting of the result. You probably have a lot of queries that require MySQL to scan whole tables or you have joins that don't use keys properly.
Handler_read_rnd_next 1,029 M The number of requests to read the next row in the data file. This is high if you are doing a lot of table scans. Generally this suggests that your tables are not properly indexed or that your queries are not written to take advantage of the indexes you have.
Created_tmp_disk_tables 880 k The number of temporary tables on disk created automatically by the server while executing statements. If Created_tmp_disk_tables is big, you may want to increase the tmp_table_size value to cause temporary tables to be memory-based instead of disk-based.
Select_full_join 107 k The number of joins that do not use indexes. If this value is not 0, you should carefully check the indexes of your tables.
Sort_merge_passes 3 The number of merge passes the sort algorithm has had to do. If this value is large, you should consider increasing the value of the sort_buffer_size system variable.
Opened_tables 74 k The number of tables that have been opened. If opened tables is big, your table cache value is probably too small.
Table_locks_waited 53 k The number of times that a table lock could not be acquired immediately and a wait was needed. If this is high, and you have performance problems, you should first optimize your queries, and then either split your table or tables or use replication.