INDIVIDUAL CPU CORE UTILIZATION

MS-SQLOperating SystemSQL

Symptoms:

Slow SQL responses have degraded, due to CPU core overload.

Impact: Medium

Description:

This alert works together with the HOST: CPU CORES UTILIZATION alert which reports average utilization across all cores, by reporting utilization per individual core.

Possible causes

Long system tasks – Priority: Medium
Unusual levels of CPU load activities may be coming from external operations (anti-virus scans, backups, restores, etc from networked data stores)
Recommended action :
Identify the source of the load (using built-in OS tools such as PerfMon) and if it is recurrent, try to reschedule to a time of low user demand.

Long SQL tasks – Priority: Medium
Identify the source of the load (using built-in OS tools such as PerfMon) and if it is recurrent, try to reschedule to a time of low user demand.

SQL Processes started to load CPU due to long tasks performed such as :

  • accessing data where indexes are missing or corrupt (causes long loops)
  • pulling large volumes of data (results in many threads or long loops)
  • coding problems (inefficient organization, missing indexes causing many threads or long loops

Recommended action :

See our recommendations regarding deadlocks here and free memory here.

 

Background

Distribution of workload over available server cores is handled by the kernel of the OS not SQL itself, and this can result in some cores running fully loaded while others are nearly idle. The other AimBetter alert for core usage reports on average workload across all cores, and sometimes may show that load is low, while individual cores are in fact running at or near 100%. This alert reports on individual cores that cross the threshold.

Share with friends:

You may also like this:

RECENT POSTS

Menu