What is SQL Server CXPACKET vs CXCONSUMER wait internal difference?
Updated May 17, 2026
Short answer
CXPACKET represents parallel worker synchronization, while CXCONSUMER represents benign consumer-side waits.
Deep explanation
In parallel query execution, SQL Server splits work into threads. CXPACKET occurs when threads wait for others in a parallel exchange operator. Historically it was considered a bottleneck, but modern SQL Server versions introduced CXCONSUMER to separate harmless waiting from actual imbalance. CXCONSUMER represents consumer threads waiting for producers and is typically not a performance issue. Real problems arise when producer threads are skewed due to uneven data distribution or bad parallel plans.
Unlock with a Pro subscription to view this section.
View pricingReal-world example
No real-world example available yet.
Unlock with a Pro subscription to view this section.
Upgrade to ProCommon mistakes
No common mistakes listed yet.
Unlock with a Pro subscription to view this section.
Upgrade to ProFollow-up questions
No follow-up questions available yet.
Unlock with a Pro subscription to view this section.
Upgrade to Pro