SQL Server with Mr. Denny

Dec 17 2009   11:00AM GMT

CXPacket isn’t the cause, it is a symptom

Denny Cherry Denny Cherry Profile: Denny Cherry

All to often when people deal with parallel queries they see that some threads of the query have a wait type of CXPacket so they assume that the parallel execution plan is causing a problem, but it probably isn’t.

What is causing the problem is the threads which don’t have a wait type of CXPACKET.  They probably have an IO, or Scheduler wait happening and the other threads can’t resume processing until that wait condition has been resolved.

Changing the query to only use a single thread will mask this because the query now only has a single thread so it is easier to identify the paused thread as it is the only thread running.  What you actually want to do to resolve this is look into the wait type of the thread which is still running and see what is holding up that thread, resolve that issue and the CXPACKET waits should then go away.

Denny

 Comment on this Post

 
There was an error processing your information. Please try again later.
Thanks. We'll let you know when a new response is added.
Send me notifications when other members comment.

REGISTER or login:

Forgot Password?
By submitting you agree to receive email from TechTarget and its partners. If you reside outside of the United States, you consent to having your personal data transferred to and processed in the United States. Privacy

Forgot Password

No problem! Submit your e-mail address below. We'll send you an e-mail containing your password.

Your password has been sent to: