|
Measures reported by MySqlLockTest
The locking activity of a database server
must be monitored carefully because an application holding a specific lock
for a long time could cause a number of other transactions relying on the
same lock to fail. The MySqlLockTest monitors the locking activity on
a database server instance.
| Measurement |
Description |
Measurement
Unit |
Interpretation |
| Pct_lock_waits |
The
percentage of lock requests that could not be satisfied
immediately and hence, required the caller to wait before being
granted the lock
|
Percent |
A
high value of waits can have an adverse impact on application
performance. Possible reasons for this behavior could be:
- inadequate number of locks available in the database,
- unusually high locking behavior of applications
accessing the database,
- improper database application design, etc.
|
| Table_locks_waited |
The
number of times in the last measurement period a table lock could not be acquired immediately and a
wait was needed |
Number
|
If the number of waits is high, application performance could suffer. You should
first optimize your queries, and then either split your table(s) or use
replication.
|
|