SAP Knowledge Base Article - Preview

2456551 - High threads/engine CPU usage and Spinlock contention - SAP ASE


  •  There is high engine thread utilization as per this sysmon output



  •     The first consideration would be to check for spinlock contention in the sp_sysmon output as shown here in the  default data cache subsection under Data Cache Management.


  • The next consideration is to try and partition the cache with sp_cacheconfig to create more spinlocks. Look up the cache configuration with sp_cacheconfig.
  • But default data cache is already partitioned 16 ways and there are only 16 engines according to the output of sp_helpthread. It is not useful to have more spinlocks/partitions than engines.


  • There is also no spinlock contention showing up in the Metadata Cache section.



  • SAP Adaptive Server Enterprise (ASE)
  • SAP Adaptive Server Enterprise Cluster Edition (ASE CE)


SAP Adaptive Server Enterprise all versions


high CPU, high kernel utilization,  Engine Utilization,  spinlock contention, system hung, ASE hangs, performance, slow , KBA , BC-SYB-ASE , Sybase ASE Database Platform (non Business Suite) , Problem

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.