eG Monitoring
 

Measures reported by IfxLockTest

This test reports the lock related measues of an Informix database server.

The measures made by this test are as follows:

Measurement Description Measurement Unit Interpretation
Lock_requests The number of lock requests received Locks/sec A high value indicates that there is high locking activity in the system and may need close scrutiny for the type of locks being requested. The detailed diagnosis for this measure, provides a list of top 10 user sessions holding maximum number of locks.
Lock_waits The number of lock waits Waits/sec 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.
Lock_timeouts The number of locks that timed out Timeouts/sec Lock timeouts can be useful for removing tasks that acquire some locks, and then wait for long periods of time blocking other users.
Deadlocks The number of deadlocks Deadlocks/sec

A deadlock may arise due to various situations including bad design of queries and deficient coding practices.

A deadlock is a situation where both/all the lock requestors are in a mutual or a multi-way tie. Any deadlocks are detrimental to database application performance.

The detailed diagnosis of this measure, if enabled, will report the details of user sessions performing deadlocks.