Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
Analyzer
Posting Yak Master
115 Posts |
 Posted - 2007-07-24 : 07:27:36
|
| CXPACKET wait type current makes up 63% of all the wait types which is causing latency. I need to identify the specific workloads responsible for waits so I can optimise or MAXDOP them. I already know how to retreived the top IO, CPU, Memory consuming queries but how do I identify the statements and order them by wait time?Can someone point me in the direction of a command, DMV or will the top CPU list be adequate? Thanks |
|
|
rmiao
Master Smack Fu Yak Hacker
7266 Posts |
Posted - 2007-07-24 : 14:36:01
|
| May need set profiler trace for this. |
 |
|
|
graz
Chief SQLTeam Crack Dealer
4149 Posts |
Posted - 2007-07-24 : 15:15:25
|
| CXPACKET waits aren't necessarily bad. It just means that one thread finished before another did. If you lower the MAXDOP the entire query will almost certainly take longer. When I look at wait stats I usually ignore this one. It isn't blocking anything.===============================================Creating tomorrow's legacy systems today.One crisis at a time. |
|
|
|
Analyzer
Posting Yak Master
115 Posts |
Posted - 2007-07-25 : 05:45:23
|
| OK thanks for the feedback. Through benchmarking we have identified the which parallelism levels provide the best performance for different workloads, problem is there all different so the server setting doesn't help in all cases. I'll monitor the situation for a while longer |
|
|
|
|
|
|
Chronic CXPACKET Wait Issue