Performance - Transaction Management Statistics
The following transaction management statistics are displayed in the Performance output window:
| Statistics | Description |
|---|---|
| Transaction commits | This is the total number of successful read/write transaction commits since the database was started. |
| Read-only commits | This is the total number of successful read-only transactions since the database was started. |
| Transaction checks | A high proportion of transaction checks in relation to the total number of transactions may indicate poorly-designed applications, with long transactions which are more likely to give rise to transaction conflicts. |
| Transaction aborts | This is the total number of transactions that have been aborted by the optimistic concurrency protocol since the database was started. User requested transaction aborts are not counted in this total. |
| Pending restarts | This is an indication of the amount of information stored in TRANSDB that relates to previous database startups. The number of restarts is counted for each databank used in a transaction. This figure grows larger when shadows are suspended. There should be no pending restarts if all the databanks have been accessed and there are no suspended shadows. |
See Also