Help me understand my wait stats.

  • Row WaitType Wait_Seconds Resource_Seconds Signal_Seconds WaitCount Percentage Avg Wait Seconds Avg Res Seconds Avg Sig Seconds
    1 CXPACKET 589948.94 570810.50 19138.43 345459657 47.68 0.0017 0.0017 0.0001 
    2 PAGELATCH_EX 208483.86 178007.43 30476.44 5792692289 16.85 0.0000 0.0000 0.0000 
    3 PAGELATCH_SH 148325.81 120946.88 27378.93 5338779307 11.99 0.0000 0.0000 0.0000 
    4 WRITELOG 97564.14 96075.60 1488.54 44147954 7.88 0.0022 0.0022 0.0000 
    5 ASYNC_NETWORK_IO 67784.65 67248.08 536.57 47742563 5.48 0.0014 0.0014 0.0000 
    6 ASYNC_IO_COMPLETION 31958.75 31958.51 0.24 20825 2.58 1.5346 1.5346 0.0000 
    7 BACKUPBUFFER 25527.95 25413.91 114.04 19409950 2.06 0.0013 0.0013 0.0000 
    8 LATCH_EX 21692.23 18961.47 2730.76 230726223 1.75 0.0001 0.0001 0.0000 

    Do these wait stats suggest Tempdb pressure? I have 8 tempDB files at the moment.

  • PretendDBA - Tuesday, February 28, 2017 3:50 PM

    Row WaitType Wait_Seconds Resource_Seconds Signal_Seconds WaitCount Percentage Avg Wait Seconds Avg Res Seconds Avg Sig Seconds
    1 CXPACKET 589948.94 570810.50 19138.43 345459657 47.68 0.0017 0.0017 0.0001 
    2 PAGELATCH_EX 208483.86 178007.43 30476.44 5792692289 16.85 0.0000 0.0000 0.0000 
    3 PAGELATCH_SH 148325.81 120946.88 27378.93 5338779307 11.99 0.0000 0.0000 0.0000 
    4 WRITELOG 97564.14 96075.60 1488.54 44147954 7.88 0.0022 0.0022 0.0000 
    5 ASYNC_NETWORK_IO 67784.65 67248.08 536.57 47742563 5.48 0.0014 0.0014 0.0000 
    6 ASYNC_IO_COMPLETION 31958.75 31958.51 0.24 20825 2.58 1.5346 1.5346 0.0000 
    7 BACKUPBUFFER 25527.95 25413.91 114.04 19409950 2.06 0.0013 0.0013 0.0000 
    8 LATCH_EX 21692.23 18961.47 2730.76 230726223 1.75 0.0001 0.0001 0.0000 

    Do these wait stats suggest Tempdb pressure? I have 8 tempDB files at the moment.

    It depends on what pages the 2 and 3 items are latching on. They could be from causes other than tempdb allocation pages, although that is often what they are related to.

    You have enough of them (unless you server has been up for a very long time) to probably see them in real-time using sp_whoisactive. You can also set up a job to put the output from that into a table for later analysis. Review Adam Machanic's 30-day blog post series to learn how to use that AWESOME free tool.

    Best,
    Kevin G. Boles
    SQL Server Consultant
    SQL MVP 2007-2012
    TheSQLGuru on googles mail service

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

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