Kbase P123689: Using -NL (No-Lock) with promon utility
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
07/11/2007 |
|
Status: Verified
GOAL:
Should Promon be used with -NL on a high transaction system?
GOAL:
Can promon be run with a no-lock option?
GOAL:
What is the -NL parameter?
FACT(s) (Environment):
OpenEdge 10.x
FIX:
Promon by default does some locking on latches when obtaining data. This behavior could cause some contention and show an increase in latch counts when proactively monitoring a database that is running in multi-user mode. It is recommended to start the promon utility with the -NL (No-Lock) option to negate this influence.
The recommendation to run promon with the -NL parameter is specifically provided for investigating lock contention issues (eg: LKT). It should not be used by default and when running promon with -NL, crashes need to be ignored.
There are other places in promon where latching is not used (eg _Lock) and promon crashes or incomplete data are returned. Starting the promon session with -NL is no different to this existing behaviour, except that it now can happen in more places potentially. The main areas are buffer pool statistics and locking statistics.