Waiting for CXpacket is normal behaviour for a parallelized query. Appearently there was a in the past, where one(!) of the indications was waiting on the type: the real problem was in the underlying sort.

It makes sense to look at the query plan, and try to figure out what those subqueries/queryslaves or whatever you want to call them are doing for this waiting thread.

If overall performance degrades, the you might run into other bottlenecks: for instance if those parallel queries run on the same disk (or small set of disks) a disk bottleneck is easily reached..

Or they simply block other threads from doing work..

BTW, most of the reference to a 'cxpacket' problem refer to the same Q&A which refer to the 'bug' but it also notes that a subquery might be waiting for 'traditional' reasons: in which I read: no bug..

good luck,

Mario