Skip to Content.
Sympa Menu

ndt-users - Packets arriving out-of-order - which direction?

Subject: ndt-users list created

List archive

Packets arriving out-of-order - which direction?


Chronological Thread 
  • From: Clarke Morledge <>
  • To:
  • Subject: Packets arriving out-of-order - which direction?
  • Date: Thu, 13 Dec 2007 17:33:14 -0500 (EST)

I am trying to interpret some of the output from NDT (v5.4.8) that indicates assymetrical performance variance. The key component for me is the line below:

"No packet loss - but packets arrived out-of-order 12.58% of the time"

But the problem I have is that it isn't clear to me where the packets are arriving out-of-order. In this case I am assuming that it is from the client-to-server direction, but could there also be some out-of-order in the server-to-client direction, too? The output isn't clear.

However, is the packets arriving out-of-order component really helping me to diagnose the assymetry problem, or is this a red herring? Is there some relevant web-100 variable(s) that I should be looking at instead?

Thanks.
-----------------------

WEB100 Enabled Statistics:
Checking for Middleboxes . . . . . . . . . . . . . . . . . . Done
checking for firewalls . . . . . . . . . . . . . . . . . . . Done
running 10s outbound test (client-to-server [C2S]) . . . . . 40.08Mb/s
running 10s inbound test (server-to-client [S2C]) . . . . . . 134.32Mb/s

------ Client System Details ------
OS data: Name = Windows XP, Architecture = x86, Version = 5.1
Java data: Vendor = Sun Microsystems Inc., Version = 1.6.0_02

------ Web100 Detailed Analysis ------
622 Mbps OC-12 link found.
Link set to Full Duplex mode
No network congestion discovered.
Good network cable(s) found
Normal duplex operation found.

Web100 reports the Round trip time = 3.27 msec; the Packet size = 1460 Bytes; and
No packet loss - but packets arrived out-of-order 12.58% of the time
C2S throughput test: Packet queuing detected: 0.00%
S2C throughput test: Excessive packet queuing detected: 10.87%
This connection is receiver limited 58.26% of the time.
Increasing the the client's receive buffer (63.0 KB) will improve performance
This connection is sender limited 41.27% of the time.

-------------------------------------------------------------

Clarke Morledge
College of William and Mary
Information Technology - Network Engineering
Jones Hall (Room 18)
Williamsburg VA 23187




Archive powered by MHonArc 2.6.16.

Top of Page