January 19, 2005 at 6:07 pm
I have a job running on my production system
-- Parameters for sp_track_waitstats are
-- n1,n2,a1 where
-- n1 - number of times to capture waitstats - default 10
-- n2 - is the delay interval. Can be in seconds or minutes. Default 1
-- a1 - delay type. Cann be 'seconds' or 'minutes'
-- eg 10,2,seconds - runs 10 times every 2 seconds
sp_track_waitstats 1,1,seconds
The output looks as such.
DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]
Job 'Wait Time Statistics' : Step 1, 'Wait Statistics' : Began Executing 2005-01-20 07:00:00
DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]
wait_type wait_time percentage
-------------------------------------------------------------------------------- ----------------------
***total*** 132325.0 100.0
NETWORKIO 101062.0 76.4
PAGEIOLATCH_SH 12567.0 9.5
WRITELOG 8492.0 6.4
PAGEIOLATCH_EX 4921.0 3.7
LCK_M_IS 2578.0 1.9
LCK_M_IX 1984.0 1.5
PAGELATCH_EX 376.0 .3
LCK_M_S 219.0 .2
IO_COMPLETION 64.0 .0
PAGELATCH_UP 31.0 .0
PAGEIOLATCH_UP 30.0 .0
DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]
Job 'Wait Time Statistics' : Step 1, 'Wait Statistics' : Began Executing 2005-01-20 08:00:00
DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]
wait_type wait_time percentage
-------------------------------------------------------------------------------- ----------------------
***total*** 321695.0 100.0
NETWORKIO 160400.0 49.9
PAGEIOLATCH_SH 43567.0 13.5
PAGEIOLATCH_EX 39251.0 12.2
WRITELOG 35459.0 11.0
LCK_M_IS 28562.0 8.9
LCK_M_S 10937.0 3.4
PAGELATCH_EX 2360.0 .7
LCK_M_IX 704.0 .2
IO_COMPLETION 221.0 .1
PAGELATCH_UP 202.0 .1
LCK_M_X 16.0 .0
PAGELATCH_SH 15.0 .0
DBCC execution completed. If DBCC printed error messages, contact your system administrator. [SQLSTATE 01000]
As you can see, the majority of time wasted is with networkIO. Now according to the system administrators the server is running gigabit links accross the network. If this is the case, what else could I or should I be looking at that might be the cause of this?
Thanks
Hope this helps...
Ford Fairlane
Rock and Roll Detective
January 20, 2005 at 12:52 am
Check out Gert's article :
http://sqldev.net/articles/WaitTypes.htm
Johan
Learn to play, play to learn !
Dont drive faster than your guardian angel can fly ...
but keeping both feet on the ground wont get you anywhere :w00t:
- How to post Performance Problems
- How to post data/code to get the best help[/url]
- How to prevent a sore throat after hours of presenting ppt
press F1 for solution, press shift+F1 for urgent solution 😀
Need a bit of Powershell? How about this
Who am I ? Sometimes this is me but most of the time this is me
January 20, 2005 at 1:04 am
I gathered all of that, but what I am after is what could be the cause of the high networkio if the server has gigabit links running as do the client pc's.
Other than that what could cause the networkio to be so high?
Hope this helps...
Ford Fairlane
Rock and Roll Detective
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply