Incorrect (zero) values are reported for "acquire blocks" and "mutex wait" counters in the fb_lock_print output [CORE3686]

[firebird-automations]

Submitted by: @dyemanov

When accessing the lock table, the local mutex is acquired first and only then the shared mutex is acquired. If all the connections belong to the single address space (SS and SC architectures), all the contention is on the local mutex, not on the shared mutex. But the local mutex "blocks" are not encounted in the statistics, hence both "acquire blocks" and "mutex wait" counters will be always zero in this case, making it hard to analyze the possible performance bottlenecks (this is mostly true for SC, as SS is almost never LM bound).

Commits: 758bb0d 448f187

[firebird-automations]

Modified by: @dyemanov

assignee: Dmitry Yemanov [ dimitr ]

[firebird-automations]

Modified by: @dyemanov

status: Open [ 1 ] => In Progress [ 3 ]

[firebird-automations]

Modified by: @dyemanov

Fix Version: 2.5.2 [ 10450 ]

Fix Version: 3.0 Alpha 1 [ 10331 ]

[firebird-automations]

Modified by: @dyemanov

status: In Progress [ 3 ] => Open [ 1 ]

[firebird-automations]

Modified by: @dyemanov

status: Open [ 1 ] => Resolved [ 5 ]

resolution: Fixed [ 1 ]

[firebird-automations]

Modified by: @pcisar

status: Resolved [ 5 ] => Closed [ 6 ]

[firebird-automations]

Modified by: @pavel-zotov

status: Closed [ 6 ] => Closed [ 6 ]

QA Status: No test