Re: high networkio in waitstats
From: Andrew J. Kelly (sqlmvpnooospam_at_shadhawk.com)
Date: 12/25/04
- Next message: Daniel Joskovski: "Re: Checkpointing Not Happening in Simple Recovery Model"
- Previous message: Dan: "dual processor license"
- In reply to: Hassan: "Re: high networkio in waitstats"
- Next in thread: John Bell: "Re: high networkio in waitstats"
- Messages sorted by: [ date ] [ thread ]
Date: Sat, 25 Dec 2004 18:46:37 -0500
If the bottleneck is that the clients or subscribers can not process the
packets fast enough it won't do any good to try and send them even faster.
The ability to process the requests fromt he server are not just network
card related. What ever process is reading those packets and subsequently
doing something with that data needs to be optimized to handle the load. It
may be something as simple as the disk drives on the clients can not handle
the load and that is backing everything up from there. But you need to
investigate each machine to see where the bottleneck is before you can
address it. Simply throwing hardware at a problem is not good unless you
know what the actual bottleneck is so you can throw the right hardware at
it. Or better yet tune the process so it is more efficient. If you are
doing a lot of replication you need to ensure your log files are on a fast
drive array that is not encumbered by other processes or files and that the
disk queues are almost non-existent. Once you are sure that is not an issue
you can work your way up to the other drives, cpu etc to ensure you don't
have any bottlenecks. It is certainly possible that the network has issues
and can't handle the load but it is usually the case that the clients are
the source of the problems and not the server in cases like this.
-- Andrew J. Kelly SQL MVP "Hassan" <fatima_ja@hotmail.com> wrote in message news:uPWcO0r6EHA.2192@TK2MSFTNGP14.phx.gbl... > So what can we do in this case ? Is it something that we can control from > the SQL Server end or the client ? So are you saying that even if we had a > 1Gbps NIC card, the problem still remains. Yes this server is a subscriber > and is receiving replicated transactions > > > "Andrew J. Kelly" <sqlmvpnooospam@shadhawk.com> wrote in message > news:uwHRbap6EHA.2016@TK2MSFTNGP15.phx.gbl... >> I agree with Anthony on this. The client plays a large role is how >> efficiently the packets get processed. Especially with heavy >> replication. > I >> have seen very high network waits on systems where the subscribers or the >> distributor can not keep up with the requests. >> >> -- >> Andrew J. Kelly SQL MVP >> >> >> "AnthonyThomas" <Anthony.Thomas@CommerceBank.com> wrote in message >> news:eSVDgdl6EHA.3708@TK2MSFTNGP14.phx.gbl... >> > Not to say that you are not maxed out on your NIC's throughput, but >> > measure >> > it with perf mon. >> > >> > Typically, the Network IO wait states are due to the client's ability >> > to >> > process the packets, especially when there is a VERY large TDS stream. >> > >> > Take a look at the clients' CPU usage. If it is high, they are not >> > processing the results quick enough. >> > >> > Sincerely, >> > >> > >> > Anthony Thomas >> > >> > >> > -- >> > >> > "Hassan" <fatima_ja@hotmail.com> wrote in message >> > news:uvvi1Aj6EHA.3944@TK2MSFTNGP12.phx.gbl... >> > My waitstats reveal a high percentage of networkIO. Currently my >> > adapter >> > is >> > a 100Mbps. Do I need a 1Gbps adapter ? How can I find out why theres a >> > high >> > wait of networkIO and what can I do to resolve it ? >> > >> > Thanks >> > >> > >> >> > >
- Next message: Daniel Joskovski: "Re: Checkpointing Not Happening in Simple Recovery Model"
- Previous message: Dan: "dual processor license"
- In reply to: Hassan: "Re: high networkio in waitstats"
- Next in thread: John Bell: "Re: high networkio in waitstats"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
