Jeff,
Nothing is going sideways. We're not theorising about problems with monLocks we're only relaying findings.
If it shouldn't be performing like this then we need to work out what the problem is.
Can you fire up a simple test on 15.7 SP132 with a single spid holding 4 million locks row on one table (just a single integer column) and post the statistics output?
The last time I checked this a few months ago I got:
==================== Lava Operator Tree ====================
Emit
(VA = 2)
r:1 er:1
cpu: 0
/
ScalarAgg
Count
(VA = 1)
r:1 er:1
cpu: 5562500
/
TableScan
master..monLocks
(VA = 0)
r:4e+06 er:100
l:0 el:10
p:0 ep:2
============================================================
Table: master..monLocks scan count 1, logical reads: (regular=0 apf=0 total=0), physical reads: (regular=0 apf=0 total=0), apf IOs used=0
Total writes for this command: 0
Execution Time 55625.
Adaptive Server cpu time: 5562311 ms. Adaptive Server elapsed time: 5562722 ms.
versus:
cpu: 0
/
ScalarAgg
Count
(VA = 1)
r:1 er:1
cpu: 400
/
TableScan
master..syslocks
(VA = 0)
r:4e+06 er:100
l:4.367e+06 el:10
p:0 ep:3
============================================================
Table: master..syslocks scan count 1, logical reads: (regular=4366948 apf=0 total=4366948), physical reads: (regular=0 apf=0 total=0), apf IOs used=0
Total writes for this command: 235
Execution Time 118.
Adaptive Server cpu time: 11811 ms. Adaptive Server elapsed time: 11863 ms.
Execution time: 11.87 seconds
With the entire hour and a half in this routine and burning 100% of an engine thread.
pc: 0x00000000015c7f0c upyield+0x2cc()
pc: 0x00000000017582b8 mda__traverse_lock_hashtable+0x23a()
pc: 0x000000000175805d mda__read_lock_table+0x39()
pc: 0x0000000001758022 mda_populate_monLocks+0x82()
pc: 0x000000000174bc14 mda_exec+0xb2()
pc: 0x0000000001722193 VTABRemoteAccess::getNext()+0x509()
pc: 0x0000000001721b5a VTABRemoteAccess::startScan(short, short, bool)+0x112()
pc: 0x000000000084b751 LeScanOp::_LeOpNext(ExeCtxt&)+0x6b1()
pc: 0x00000000008149ca LeEmitSndOp::_LeOpNext(ExeCtxt&)+0x1ba()
pc: 0x00000000007fe83a LePlanNext+0xfa()
[Handler pc: 0x0x0000000000fb3520 le_execerr installed by the following function:-]
pc: 0x0000000000fbf450 exec_lava+0x280()
pc: 0x00000000011686ca s_execute+0x171a()
[Handler pc: 0x0x000000000120ad00 hdl_stack installed by the following function:-]
[Handler pc: 0x0x00000000011a5e30 s_handle installed by the following function:-]
pc: 0x00000000011aa8f2 sequencer+0x2532()
pc: 0x00000000007cb9a9 tdsrecv_language+0x189()
[Handler pc: 0x0x00000000014ed3b0 ut_handle installed by the following function:-]
pc: 0x00000000007ebd40 conn_hdlr+0x10c0()
dbcc stacktrace finished.
Our team is responsible for (along with about a million other things!) monitoring 200+ ASE servers. We simply cannot use monLocks.
If this is something specific to our cfg I would be keen to know.