CXPACKET

Description

A lot of the long running queries are being parallelized. This is not necessarily a bad thing but it does consume additional CPU resources. If processor utilization is very high (typically above 80%) this wait should be investigated

Resolved by

DBAs and Developers

Suggested solutions

  1. Examine high CPU queries to see if they can be optimized.
  2. Investigate changing default MAXDOP and parallelism settings (links below)
  3. Indexing, look for high CPU parallel queries

Additional research

Troubleshooting the CXPACKET wait type in SQL Server
Five SQL Server Settings to Change
What MAXDOP setting should be used for SQL Server

See more

Consider using ApexSQL Monitor, a Windows and SQL Server monitoring tool able to track SQL Server wait types, including the individual query wait statistics

⇐ Back to index