Hi all,
We need to figure out some problem due to network latency between two
sites and run netstat to see if Recv-Q and Send-Q are filling up, but
we see that they are always zero.
We forced the Recv-Q to queue up but still no luck and nestat would
still show zero.
Is this a bug in all versions of Solaris including 10 6/06?
Is there any other tool that shows us the same result as netstat? We
need to see how much Recv-Q and Send-Q queue up if network latency is
high.
Thanks,

In article <1165285073.296628.172360@f1g2000cwa.googlegroups.com>,
	"Vahid  Moghaddasi" <moghaddasi@gmail.com> writes:
> Hi all,
> We need to figure out some problem due to network latency between two
> sites and run netstat to see if Recv-Q and Send-Q are filling up, but
> we see that they are always zero.
> We forced the Recv-Q to queue up but still no luck and nestat would
> still show zero.
> Is this a bug in all versions of Solaris including 10 6/06?
> Is there any other tool that shows us the same result as netstat? We
> need to see how much Recv-Q and Send-Q queue up if network latency is
> high.

You seem to be assuming that a high latency will result in high
Recv-Q and Send-Q. This is not necessarly so. It depends on the
protocol you are running over TCP/IP, and is only likely to happen
if the protocol sends a large amount of data without waiting for any
data (in the form of an application level acknowledgement) from the
far end. Network latency doesn't have any affect on Recv-Q -- that
depends on your program's latency and how it's implemented
internally.

-- 
Andrew Gabriel

Andrew Gabriel wrote:
> You seem to be assuming that a high latency will result in high
> Recv-Q and Send-Q. This is not necessarly so.

Yes we are assuming that.

> It depends on the
> protocol you are running over TCP/IP, and is only likely to happen
> if the protocol sends a large amount of data without waiting for any
> data (in the form of an application level acknowledgement) from the
> far end. Network latency doesn't have any affect on Recv-Q -- that
> depends on your program's latency and how it's implemented
> internally.

We wrote a program which processes data very slowly on the receiving
server and
then we pumped some data from the sending server to the receiving
socket. Since the
receiving end is processing data very slowly, we expected to see the
recv-q and
eventually send-q grow up.
Thanks,