Waitopedia is a comprehensive resource of information about SQL Server waits.

The description shown below is the top answer as voted by the Spotlight community.

The charts are based on 2.1 TB of data collected from 4207 instances uploaded by 323 Spotlight users over an 8 week period.


Category: Idle
SQL Server versions: 2016, 2017

This is an idle wait and so it can be safely ignored.


1 Answer


Occurs with parallel query plans when a consumer thread waits for a producer thread to send rows. This is a normal part of parallel query execution and can be safely ignored. This wait type was added in 2016 SP2 and 2017 RTM CU3 to distinguish between actionable CXPACKET waits, that should be investigated, and benign parallel waits that can be ignored. For query plan operators that have producer and consumer threads, all threads traditionally could show CXPACKET waits. The potential performance issue is with the producer threads that suppose to produce the data and not with the consumer threads that are just waiting for that data. As such, any performance improvement should aim to make the produces provide the data faster and hence will also reduce the consumers wait time. By making the consumer threads register benign CXCONSUMER waits, the remaining CXPACKET waits from the producer threads are what indicate a performance problem.

Very rare

This wait never occurs for most instances

For each of 4207 instances, we ranked CXCONSUMER on how frequent it is compared to all other recent waits. The chart shows the total of all rankings.

Prevalence of CXCONSUMER across the Spotlight Population

For 62 % of hours with this wait, average wait time is less than 13 ms

For each instance, we found all the recent hours when it had a CXCONSUMER wait. We found the average latency for each of those hours.

28 instances contributed data to this chart

Latency Distribution of CXCONSUMER across the Spotlight Population