17. MPing on a “Normal” Path Rtt window not yet full Slope = 1 / rtt Stable queueing region Tail-drop behavior
18. MPing on a “Normal” Path Stable data rate 3600*1000*8 = 29 Mbps Queue size (280-120)*1000 = 160 KB Effective BW*Delay Product 120*1000 = 120 KB Packet Loss 1 - 3600/4800 = 25% Rtt = 120/3600 = 33 msec
19. Some MPing Results #1 RTT is increasing as load increases Slow packet processing? Fairly normal behavior Discarded packets are costing some performance loss
20. Some MPing Results #2 Very little stable queueing Insufficient memory? Spikes from some periodic event (cache cleaner?) Discarding packets comes at some cost to performance Error logging?
21. Some MPing Results #3 Fairly constant packet loss, even under light load Major packet loss, ~7/8 or 88% Hump at 50 may be duplex problem Both turned out to be an auto-negotiation duplex problem Setting to static full-duplex fixed these!
22. Some MPing Results #4 Oscillations with little loss Rate shaping? Decreasing performance with increasing queue length Typical of Unix boxes with poor queue insertion
23.
24.
25.
26.
27. Maximum Transmission Unit (MTU) Issues http://sd.wareonearth.com/woe/jumbo.html New York to Los Angeles. Round Trip Time (rtt) is about 32 msec, and let's say packet loss is 0.1% (0.001). With an MSS of 1500 bytes, TCP throughput will have an upper bound of about 8.3 Mbps! And no, that is not a window size limitation, but rather one based on TCP's ability to detect and recover from congestion (loss). With 9000 byte frames, TCP throughput could reach about 50 Mbps.
28.
29.
30.
31.
32.
33. TCP’s Sliding Window 1 2 3 4 5 6 7 8 9 10 11 ... Offered receiver window Sent and ACKed Sent, not ACKed Can send ASAP Can’t send until window moves Usable window W. R. Stevens, 20.3
57. Resources Enabling High Performance Data Transfers on Hosts: http://www.psc.edu/networking/perf_tune.html Internet Measurement Tool Taxonomy http://www.caida.org/tools/taxonomy/measurement/ http://www.oyya.synthasite.com/ http://oyya.synthasite.com/contact.php