Pinned topic Lock Monitoring Performance Issues
Answered question This question has been answered.
Unanswered question This question has not been answered yet.
Has anyone else turned on Lock Event Monitor with Statement History with values and encountered a good amount of performance impact? I've tried this twice and both times seen latency on both the database and the website.
Updated on 2011-06-27T08:09:24Z at 2011-06-27T08:09:24Z by UteBaumbach
UteBaumbach 100000HN9355 Posts
Re: Lock Monitoring Performance Issues2011-06-27T08:09:24ZThis is the accepted answer. This is the accepted answer.Hi,
yes, the Lock event monitor with statement history and values generates some recognizable overhead dependent on the workload. The reason is that DB2 has to save all statements and values of all transactions in memory in case a locking problem occurs to be able to report the statements and values for a locking problem.