Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2008
»
SQL Server 2008 - General
»
Question on Lock wait types
Question on Lock wait types
Rate Topic
Display Mode
Topic Options
Author
Message
baabhu
baabhu
Posted Sunday, October 28, 2012 9:42 PM
Ten Centuries
Group: General Forum Members
Last Login: Yesterday @ 1:58 AM
Points: 1,112,
Visits: 970
Hello Everyone,
Our production server experiences lot of blocking and locking from application.
I have attached the top waits from server. Can anyone help to understand or guide me what should be our first goal.
We cannot stop the traces for few days since we are in the midst of troubleshooting a application issue.
Other than trace wait I see a lot of waits on the OLEDB. We have Peer to peer replication setup done across networks.
wait_type waiting_tasks_count wait_time_ms
TRACEWRITE 10376534 14220260175
OLEDB 300522122 14205053714
WRITELOG 547624686 7070550328
Does this sounds too much on a OLTP systems. Or is this a normal figure.
Please let me know if I need to submit any other information.
Thank you.
Babu
Post #1378087
CapnHector
CapnHector
Posted Monday, October 29, 2012 12:50 PM
SSC Eights!
Group: General Forum Members
Last Login: Friday, May 17, 2013 10:07 AM
Points: 935,
Visits: 1,709
baabhu (10/28/2012)
Hello Everyone,
Our production server experiences lot of blocking and locking from application.
I have attached the top waits from server. Can anyone help to understand or guide me what should be our first goal.
We cannot stop the traces for few days since we are in the midst of troubleshooting a application issue.
Other than trace wait I see a lot of waits on the OLEDB. We have Peer to peer replication setup done across networks.
wait_type waiting_tasks_count wait_time_ms
TRACEWRITE 10376534 14220260175
OLEDB 300522122 14205053714
WRITELOG 547624686 7070550328
Does this sounds too much on a OLTP systems. Or is this a normal figure.
Please let me know if I need to submit any other information.
Thank you.
Babu
one thing with sys.dm_os_wait_stats (which given the format is where i think you are looking) is that they are cumulative since last server restart (or stats reset). so with out knowing how much uptime your server has had these numbers could be really low, really high, or somewhere in the middle. also if you dont have any thing to compare to these numbers may be what is normal for your server and since you are looking at them while there is a problem have no idea if its even where you should be looking.
give that you ask if its to much on a oltp system i dont think you have a server base line (which is different for every server based on what its work load is.) with out alot more information it will be hard to pinpoint what is going on.
For faster help in answering any problems Please read
How to post data/code on a forum to get the best help - Jeff Moden
for the best way to ask your question.
For performance Issues see how we like them posted here:
How to Post Performance Problems - Gail Shaw
Need to Split some strings?
Jeff Moden's DelimitedSplit8K
Jeff Moden's
Cross tab and Pivots Part 1
Jeff Moden's
Cross tab and Pivots Part 2
Jeremy Oursler
Post #1378418
baabhu
baabhu
Posted Tuesday, October 30, 2012 11:31 AM
Ten Centuries
Group: General Forum Members
Last Login: Yesterday @ 1:58 AM
Points: 1,112,
Visits: 970
capnhector (10/29/2012)
baabhu (10/28/2012)
Hello Everyone,
Our production server experiences lot of blocking and locking from application.
I have attached the top waits from server. Can anyone help to understand or guide me what should be our first goal.
We cannot stop the traces for few days since we are in the midst of troubleshooting a application issue.
Other than trace wait I see a lot of waits on the OLEDB. We have Peer to peer replication setup done across networks.
wait_type waiting_tasks_count wait_time_ms
TRACEWRITE 10376534 14220260175
OLEDB 300522122 14205053714
WRITELOG 547624686 7070550328
Does this sounds too much on a OLTP systems. Or is this a normal figure.
Please let me know if I need to submit any other information.
Thank you.
Babu
one thing with sys.dm_os_wait_stats (which given the format is where i think you are looking) is that they are cumulative since last server restart (or stats reset). so with out knowing how much uptime your server has had these numbers could be really low, really high, or somewhere in the middle. also if you dont have any thing to compare to these numbers may be what is normal for your server and since you are looking at them while there is a problem have no idea if its even where you should be looking.
give that you ask if its to much on a oltp system i dont think you have a server base line (which is different for every server based on what its work load is.) with out alot more information it will be hard to pinpoint what is going on.
Thank you very much for your suggestion. How do we define a baseline. I know it's hard to tell without much of information.
Can you share how do you do for your PROD servers. Based on that I will define our prod baseline.
Post #1378918
GilaMonster
GilaMonster
Posted Tuesday, October 30, 2012 11:32 AM
SSC-Dedicated
Group: General Forum Members
Last Login: Today @ 3:08 PM
Points: 37,720,
Visits: 29,973
Chapter 1:
http://www.simple-talk.com/books/sql-books/troubleshooting-sql-server-a-guide-for-the-accidental-dba/
Gail Shaw
Microsoft Certified Master: SQL Server 2008, MVP
SQL In The Wild
: Discussions on DB performance with occasional diversions into recoverability
We walk in the dark places no others will enter
We stand on the bridge and no one may pass
Post #1378921
Gail Wanabee
Gail Wanabee
Posted Wednesday, October 31, 2012 12:13 PM
SSC Veteran
Group: General Forum Members
Last Login: Monday, May 06, 2013 2:26 PM
Points: 254,
Visits: 1,029
This page from Paul Randal's blog may assist you:
http://www.sqlskills.com/blogs/paul/post/Wait-statistics-or-please-tell-me-where-it-hurts.aspx
Post #1379480
scogeb
scogeb
Posted Wednesday, October 31, 2012 2:00 PM
Valued Member
Group: General Forum Members
Last Login: Thursday, May 16, 2013 10:08 AM
Points: 64,
Visits: 315
Lee Crain (10/31/2012)
This page from Paul Randal's blog may assist you:
http://www.sqlskills.com/blogs/paul/post/Wait-statistics-or-please-tell-me-where-it-hurts.aspx
Cool article, thanks for posting it!
One of the main servers I deal with has CXPACKET waits of about 60%. I've told the developers which SPs have a bunch, but they have yet to change the maxdop on them. It will be interesting to see how much that helps performance.
Post #1379517
George M Parker
George M Parker
Posted Wednesday, October 31, 2012 2:22 PM
Mr or Mrs. 500
Group: General Forum Members
Last Login: Thursday, May 09, 2013 1:13 PM
Points: 516,
Visits: 1,004
scogeb (10/31/2012)
Lee Crain (10/31/2012)
This page from Paul Randal's blog may assist you:
http://www.sqlskills.com/blogs/paul/post/Wait-statistics-or-please-tell-me-where-it-hurts.aspx
Cool article, thanks for posting it!
One of the main servers I deal with has CXPACKET waits of about 60%. I've told the developers which SPs have a bunch, but they have yet to change the maxdop on them. It will be interesting to see how much that helps performance.
CXPACKET waits are not necessarily a bad thing, sometimes they occur when one parallel thread takes longer to execute a porttion of a task than other threads. That can easily occur when the distribution of data is uneven and more work is handed off to one scheduler than another. Some potential sources that you can look for are table scans that are occurring because of missing indexes or out of date distribution statistics that lead to poor query plans being created.
One thing that you might consider is setting the cost threshold for paralellism higher so that fewer queries run in parallel but you would want to test that out thoroughly in a test environment first because it could actually make overall performance worse.
Or as you suggest, you can get the developers to override MAXDOP inside of the offending stored procedures.
Post #1379524
baabhu
baabhu
Posted Thursday, November 01, 2012 2:04 AM
Ten Centuries
Group: General Forum Members
Last Login: Yesterday @ 1:58 AM
Points: 1,112,
Visits: 970
Thank you very much everyone.
Post #1379660
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.