MySQL anomalies

The MySQL collector allows to insert the following types of anomalies in an Anomalies profile:

Aborted connections
Number of connections aborted because the client died without closing the connection properly.
Failed connections
Number of tries to connect to the MySQL Server that failed
Key cache hit rate
Percentage of times a key read is handled from the key buffer cache.
Key buffer used (%)
Percentage of key buffer cache used
Tables opened
Number of opened table. If the number of opened tables is high, your cache
may be too small (table_cache parameter).
Table locks waited
Number of times 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 optimise your queries, and then either split your
table(s) or use replication.
Select full join
The number of joins that do not use indexes.
Slow query
Number of queries that have taken more than slow_launch_time to create.
Read next row in the datafile
The number of requests to read the next row in the data file. This will be 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.
Sort merge pass
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.

Go back to the Learning center:

Copyright © AgileLoad. All rights reserved.
Agile Load testing tool| Contact AgileLoad | Terms of Use | Sitemap