Symptom
- High spinlock contention in SSQLCACHE_SPIN
- Thousand of duplicate statement causing bloat in statement cache are not reused due to:
- using derived table statement with a literal which are not autoparamed
- using isnull with a literal which are not autoparamed
- using permanent temp tables with a unique table name
- Spinlocks show contention on the main spinlock which is 16
SpinlockNum SpinlockName Grabs Spins Waits SpinsPerWait Contention
----------- ------------------------------ -------------------- -------------------- -------------------- --------------- ----------
9 SSQLCACHE_SPIN[i] 80652 4044 108 37.00 0.13
13 SSQLCACHE_SPIN[i] 73377 1213 59 20.00 0.08
7 SSQLCACHE_SPIN[i] 72320 3434 106 32.00 0.14
16 SSQLCACHE_SPIN[i] 54461 1065771505 19164 55613.00 35.18
3 SSQLCACHE_SPIN[i] 47131 5516 206 26.00 0.43
8 SSQLCACHE_SPIN[i] 45091 1700 63 26.00 0.13
15 SSQLCACHE_SPIN[i] 41171 1825 51 35.00 0.12
4 SSQLCACHE_SPIN[i] 37605 71856 144 499.00 0.38
2 SSQLCACHE_SPIN[i] 32944 1221 59 20.00 0.17
1 SSQLCACHE_SPIN[i] 23843 475 13 36.00 0.05
12 SSQLCACHE_SPIN[i] 23549 669 23 29.00 0.09
5 SSQLCACHE_SPIN[i] 21349 361 11 32.00 0.05
14 SSQLCACHE_SPIN[i] 17575 138 6 23.00 0.03
11 SSQLCACHE_SPIN[i] 15276 325 2 162.00 0.01
6 SSQLCACHE_SPIN[i] 14386 197 14 14.00 0.09
10 SSQLCACHE_SPIN[i] 14148 52 3 17.00 0.02
Read more...
Environment
Adaptive Server Enterprise (ASE) 16.0 SP04
Product
Keywords
bloat, CR 831397, 831397, spinlock, contention , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Product Enhancement
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.
SAP Knowledge Base Article - Preview