Lock Diagnostics Read

The Lock Diagnostics Read category provides summary information about database read lock usage. You can use this information when analyzing system performance.

Unlike write locks, read lock usages can exceed 100%. This can occur due to multiple threads of execution each holding a read lock for the duration of the measurement period.

Priority is given to write locks, so a read lock might be relinquished after a short period if a database write is waiting. Any new read lock request will wait until all pending write locks have completed. This might result in a number of read locks occurring before a particular read activity is completed. This only occurs if temporary release of the database read lock is feasible - this is not suitable for some read activities (which need to retain their read lock to completion).

For status information regarding locks in Geo SCADA Expert, see Locks. The Locks category displays all locks within the server, whereas database locks are specific to the 'database' and assist in identifying which operation is causing high lock utilization.

The database read locks are shown in rows, with each row representing a different lock. The status information shown for each lock is as follows:

You can access a context-sensitive menu by right-clicking on an entry in the list.

The options that are available are:

ATTENTION: These menu options apply to both database read and database write locks together. So, for example, the Reset Lock Diagnostics option will reset the write lock diagnostics and the read lock diagnostics.

Further Information

Priority of Write Locks over Read Locks: see Lock Diagnostics Write.


Disclaimer

Geo SCADA Expert 2022