RE: N/w Bottleneck Check under Benchmark Load ?

1) take separate deltas for all those different figures
 
2) yes you need to gather this data in db server
 
3) identify the network interface cards through which your test traffic goes
and use netstat on those only (netstat -i should allow you to specify
network interfaces to measure)

--
Regards,
Tanel Poder
http://blog.tanelpoder.com <http://blog.tanelpoder.com/> 


 


  _____  

From: VIVEK_SHARMA [mailto:VIVEK_SHARMA@xxxxxxxxxxx] 
Sent: Tuesday, June 24, 2008 17:26
To: tanel.poder.003@xxxxxxx; 'ORACLE-L'; mwf@xxxxxxxx; tim@xxxxxxxxx
Subject: RE: N/w Bottleneck Check under Benchmark Load ?



Thanks V much Tanel for responding, as always

 

Qs 1 Towards calculating the TCP Traffic delta, From the netstat -f inet -p
tcp" Output (sample below), Is adding the TOP 3 Values "in bytes" reasonable
enough?

 

Qs 2 Should these readings be taken from the DB Server since it is at one
end of the configuration Chain? 

Config Chain Diagram:-

Load Generator m/c <-> APP Servers <-> DB Server m/c

 

Qs 3 Additionally the APP Server has multiple Network Cards. How is the
amount of TCP Traffic sent/received to/from the APP to the DB Server to be
Calculated?

NOTE - Command "netstat -f inet -p tcp" does NOT have an IP Address
specification

 

Cheers

 

Vivek

 

P.S. "netstat -f inet -p tcp" Sample Output:-

tcp:
      4065625909 packets sent
            3774590048 data packets (4134580083 bytes)
            24539 data packets (21547168 bytes) retransmitted

...

      711924647 packets received
            4006391082 acks (for 4141693631 bytes)
            2497169 duplicate acks
            0 acks for unsent data
            126381026 packets (2263129970 bytes) received in-sequence

 

 


  _____  


From: Tanel Poder
Sent: Tuesday, June 03, 2008 7:45 PM



Hi Vivek,

 

As I mentioned in the private reply, you need to take two snapshots of
netstat output (over 10 sec interval for example) and calculate delta
between corresponding bytes/sent values (also for bytes received values) to
see whether the TCP traffic is anywhere near your network link bandwidth. If
it is you're experiencing network link bandwidth issue. If it isn't then
it's something else (like wrong TCP buffersize settings but it could also
indicate a bottleneck in your (V)LAN infrastructure) 


Regards,
Tanel Poder


**************** CAUTION - Disclaimer *****************

This e-mail contains PRIVILEGED AND CONFIDENTIAL INFORMATION intended solely


for the use of the addressee(s). If you are not the intended recipient,
please 

notify the sender by e-mail and delete the original message. Further, you
are not 

to copy, disclose, or distribute this e-mail or its contents to any other
person and 

any such actions are unlawful. This e-mail may contain viruses. Infosys has
taken 

every reasonable precaution to minimize this risk, but is not liable for any
damage 

you may sustain as a result of any virus in this e-mail. You should carry
out your 

own virus checks before opening the e-mail or attachment. Infosys reserves
the 

right to monitor and review the content of all messages sent to or from this
e-mail 

address. Messages sent to or from this e-mail address may be stored on the 

Infosys e-mail system.

***INFOSYS******** End of Disclaimer ********INFOSYS***

Other related posts: