| Field |
Internal name |
Type |
Warn |
Crit |
Info |
| Handler write |
Handler_write |
derive |
|
|
The number of requests to insert a row in a table. |
| Handler update |
Handler_update |
derive |
|
|
The number of requests to update a row in a table. |
| Handler delete |
Handler_delete |
derive |
|
|
The number of requests to delete a row in a table. |
| Handler Read First |
Handler_read_first |
derive |
|
|
The number of times the first entry was read from an index. If this is high, it suggests that the server is doing a lot of full index scans. |
| Handler Read Key |
Handler_read_key |
derive |
|
|
The number of requests to read a row based on a key. If this is high, it is a good indication that your queries and tables are properly indexed. |
| Handler Read Next |
Handler_read_next |
derive |
|
|
The number of requests to read the next row in key order. This is incremented if you are querying an index column with a range constraint or if you are doing an index scan. |
| Handler Read Prev |
Handler_read_prev |
derive |
|
|
The number of requests to read the previous row in key order. This read method is mainly used to optimize ORDER BY ... DESC. |
| Handler Read Random |
Handler_read_rnd |
derive |
|
|
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 Random Next |
Handler_read_rnd_next |
derive |
|
|
RThe 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. |
