Scribd
Upload
28 views2 pages

SQL Server CX WAITS

The document discusses an issue where a stored procedure running on SQL Server 2022 is producing CX waits. The OP added OPTION(MAXDOP 1) hints to remove the waits, but this slowed down query performance significantly. The OP questions whether increasing the max degree of parallelism setting could help. Another user responds that CX waits are expected and not necessarily a problem on servers with multiple CPUs, unless there is an actual performance issue being experienced.

Uploaded by

levriat
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
28 views2 pages

SQL Server CX WAITS

The document discusses an issue where a stored procedure running on SQL Server 2022 is producing CX waits. The OP added OPTION(MAXDOP 1) hints to remove the waits, but this slowed down query performance significantly. The OP questions whether increasing the max degree of parallelism setting could help. Another user responds that CX waits are expected and not necessarily a problem on servers with multiple CPUs, unless there is an actual performance issue being experienced.

Uploaded by

levriat
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

17/2/24, 22:49 CX WAITS - DOP SETTINGS – SQLServerCentral Forums

Register Login  Menu

Home  Forums  SQL Server 2022  SQL Server 2022 - Administration  CX WAITS
- DOP SETTINGS

Post reply Like (0)

CX WAITS - DOP SETTINGS


krypto69 February 14, 2024 at 1:29 pm #4378556

Hi

I have a job that calls a stored proc. Every since we updated to


SQL2022 (running in 140 compatibility mode) I've noticed that
SSChampion
this and other similar procs produce a CX_PORT wait. They do
Points: 13589
this every time they run and if I check who is active there are no
 More deltas records being moved at may points in the query - they
actions always finish tho. So I added the OPTION(MAXDOP 1) hint in
many places in the statement and after I do that there are no
more CX waits and the deltas move correctly - problem is now
that the statement takes 10 times longer to complete. Which
surprised me I thought once I got the waits to go away the
statement would finish much faster.

I have my max dop setting at the server at 8 (and 8 for secondary


H/A). When I set the max DOP at the server level I followed the
MS guidelines but wondering if I need to go from 8 to 4 as a test?

Cost threshold for Parallism is set at 30

What is the most likely culprit here? I have a handful of procs all
producing the CX waits since we updated to SQL2022. I also
checked the available threads and I have over 785 available - so
I'm good there (I think).
https://www.sqlservercentral.com/forums/topic/cx-waits-dop-settings 1/2
17/2/24, 22:49 CX WAITS - DOP SETTINGS – SQLServerCentral Forums

This topic was modified 3 days, 15 hours ago by krypto69.

This topic was modified 3 days, 15 hours ago by krypto69.

CreateIn February 14, 2024 at 3:52 pm Like (0) #4378650

dexNoncl If your SQL server has more than one processor and your
ustered application is not purely OLTP, CX waits are good.

CXSYNC_PORT is a new wait type in 2022, it was happening


before in previous versions of SQL, it just wasn't recorded.

Is there an actual performance problem you are experiencing or


SSChasing
are you just trying to solve the waits?
Mays
Points: 640

 More
actions

Viewing 2 posts - 1 through 1 (of 1 total)


You must be logged in to reply to this topic. Login to reply

https://www.sqlservercentral.com/forums/topic/cx-waits-dop-settings 2/2

You might also like