Paramters:


360 pkts/stream, 10 probing rates, GAP_NS_EPSILON=1us, Q_NS_EPSILON=1us

360 pkts/stream, 10 probing rates, GAP_NS_EPSILON=0us, Q_NS_EPSILON=0us

360 pkts/stream, 6 probing rates, GAP_NS_EPSILON=1us, Q_NS_EPSILON=1us

360 pkts/stream, 6 probing rates, GAP_NS_EPSILON=0us, Q_NS_EPSILON=0us

TAU= 250ms, ETA= 2/3

Let 300Mbps cross traffic starts almost at the same time with rapid flow. Repeat three times for each set of parameters.



1. 360pkts, 10rates, gap_ns_epsilon=1us, q_ns_epsilon=1us, TAO=250ms,ETA=2/3
   link loss: 13,19,12
   tcp loss: 8,12,7
   lossy time intervals: 
Loss from 2.70448708534241 to 2.80459189414978 844 dupackes for 1330186000
Loss from 3.10733199119568 to 3.17997193336487 623 dupackes for 1348816352
Loss from 3.94118309020996 to 4.02804803848267 745 dupackes for 1405258456
Loss from 4.19033288955688 to 4.27570199966431 730 dupackes for 1412652232

Loss from 2.60250091552734 to 2.7115650177002 915 dupackes for 600022274
Loss from 4.15973401069641 to 4.2393000125885 681 dupackes for 710454626
Loss from 4.96487498283386 to 5.04222106933594 647 dupackes for 762015154
Loss from 5.71117997169495 to 5.80165910720825 766 dupackes for 811345898

Loss from 2.54664087295532 to 2.6449339389801 850 dupackes for 523936938
Loss from 2.64622592926025 to 2.65428996086121 2 dupackes for 525170914
Loss from 7.84744095802307 to 7.9462559223175 841 dupackes for 879459978

2. 360pkts, 10rates, gap_ns_epsilon=0us, q_ns_epsilon=0us, TAO=250ms,ETA=2/3
   link loss: 0,0,0
   tcp loss: 0,0,0

3. 360pkts, 6rates, gap_ns_epsilon=1us, q_ns_epsilon=1us, TAO=250ms,ETA=2/3
   link loss: 21,2,0,0
   tcp loss: 15,2,0,0
   lossy time intervals: 
Loss from 10.9188549518585 to 11.0300719738007 932 dupackes for 3049928808
Loss from 11.0315289497375 to 11.0401780605316 2 dupackes for 3051289456
Loss from 12.4678890705109 to 12.5651371479034 818 dupackes for 3115400400
Loss from 13.9970729351044 to 14.0864229202271 772 dupackes for 3184865832

Loss from 10.5346701145172 to 10.6421301364899 903 dupackes for 2081849469
Loss from 10.6433639526367 to 10.6519000530243 2 dupackes for 2083158741

no loss

noloss

4. 360pkts, 6rates, gap_ns_epsilon=0us, q_ns_epsilon=0us, TAO=250ms,ETA=2/3
   link loss: 0,0,0
   tcp loss: 0,0,0

To sum up, every deep in the throughput plot corresponds to lossy period. GAP_NS_EPSILON=1us can be every lossy! If GAP_NS_EPSILON=0, in this set of experiment no loss occurs.

Use ON/OFF UDP cross traffic, let rapid adjust to sudden decrease of avail-bw. Repeat three times for each set of parameters.



1. 360pkts, 10rates, gap_ns_epsilon=1us, q_ns_epsilon=1us, TAO=250ms,ETA=2/3
   link loss: 45,60,91
   tcp loss: 26,26,35
   lossy time intervals: 
Loss from 10.0127439498901 to 10.1194357872009 896 dupackes for 2412555537
Loss from 10.1206488609314 to 10.1255218982697 2 dupackes for 2413887697

Loss from 10.0014607906342 to 10.1129949092865 943 dupackes for 3041943209
Loss from 10.114590883255 to 10.1187059879303 2 dupackes for 3043332817
Loss from 10.7271118164062 to 10.8014788627625 642 dupackes for 3074129057
Loss from 11.4755389690399 to 11.5792288780212 887 dupackes for 3122524113
Loss from 18.4387719631195 to 18.5143849849701 653 dupackes for 3601034737

Loss from 10.0181949138641 to 10.094340801239 636 dupackes for 3683197929
Loss from 11.9189369678497 to 12.0291059017181 920 dupackes for 3804521201
Loss from 12.0299909114838 to 12.0354979038239 2 dupackes for 3805853641
Loss from 12.6078798770905 to 12.6896529197693 704 dupackes for 3828321337
Loss from 12.846195936203 to 12.9546308517456 898 dupackes for 3835136329
Loss from 13.1365787982941 to 13.2140028476715 672 dupackes for 3844512809
Loss from 13.8255138397217 to 13.9290499687195 876 dupackes for 3888094569
Loss from 14.076504945755 to 14.1814458370209 882 dupackes for 3894624305
Loss from 14.7021520137787 to 14.7894330024719 752 dupackes for 3929313553
Loss from 16.0866718292236 to 16.1762328147888 757 dupackes for 4010149361
Loss from 16.7827608585358 to 16.8675858974457 722 dupackes for 4035787457
Loss from 17.4235219955444 to 17.5301759243011 915 dupackes for 4057659745

2.  360pkts, 10rates, gap_ns_epsilon=0us, q_ns_epsilon=0us, TAO=250ms,ETA=2/3
   link loss: 41,5,24
   tcp loss: 14,4,16
   lossy time intervals: 
Loss from 9.91899394989014 to 10.0236170291901 889 dupackes for 4052924544

Loss from 10.0536360740662 to 10.1315701007843 650 dupackes for 3685821992

Loss from 9.97567987442017 to 10.0612180233002 713 dupackes for 709399825

3.360pkts, 6rates, gap_ns_epsilon=1us, q_ns_epsilon=1us, TAO=250ms,ETA=2/3
   link loss: 94,61,57,33
   tcp loss: 89,27,14,19
   lossy time intervals: 
Loss from 10.0141861438751 to 10.12149310112 904 dupackes for 2970709106
Loss from 10.1227331161499 to 10.1227951049805 6 dupackes for 2970942234
Loss from 10.1228091716766 to 10.1229031085968 5 dupackes for 2970950922
Loss from 10.1229271888733 to 10.1230380535126 7 dupackes for 2970962506
Loss from 10.1230602264404 to 10.1230971813202 5 dupackes for 2970969274
Loss from 10.1231181621552 to 10.1234321594238 5 dupackes for 2970977962
Loss from 10.3304581642151 to 10.4068491458893 662 dupackes for 2981509834
Loss from 10.6225440502167 to 10.7063221931458 716 dupackes for 2990311234
Loss from 12.2042820453644 to 12.2974410057068 773 dupackes for 3063792754

Loss from 10.0140240192413 to 10.1085741519928 789 dupackes for 476320166
Loss from 10.2325060367584 to 10.3251090049744 804 dupackes for 485595118
Loss from 11.1772270202637 to 11.2552011013031 656 dupackes for 522226582
Loss from 11.5606501102448 to 11.6711881160736 925 dupackes for 539352182
Loss from 13.7682859897614 to 13.861545085907 799 dupackes for 660031678

Loss from 9.99997401237488 to 10.0722079277039 625 dupackes for 3475009506

Loss from 9.98810601234436 to 10.0895800590515 862 dupackes for 3529657373
Loss from 10.091322183609 to 10.0983471870422 2 dupackes for 3530931893

4. 360pkts, 6rates, gap_ns_epsilon=0us, q_ns_epsilon=0us, TAO=250ms,ETA=2/3
   link loss: 22,17,34
   tcp loss: 14,13,10
   lossy time intervals: 
Loss from 10.0636210441589 to 10.1613509654999 835 dupackes for 1605402960

Loss from 10.0136978626251 to 10.1233999729156 924 dupackes for 1921639474

Loss from 10.0565099716187 to 10.1454780101776 773 dupackes for 2615681417

To sum up, if GAP_NS_EPSILON=1us, losses might occur even after ABests has been adjusted to decreasing ab. If GAP_NS_EPSILON=0us, losses only occurs at the moment when cross traffic joins in, and Rapid is able to adjust its throughput while avoid overestimation too much.

Why 6rates ramps up sluggishly?

Simply because that the highest probing rate is lower for the case with 10rates. So it takes longer time to ramp up. In one experiment which logged send gaps and receive gaps, TCP Rapid with 6rates/pstream produced a gradually increasing abests and took 100 pstreams to reach abest=1000Mbps. Assume the average abest is 400Mbps and TAU is infinite small, it takes 2.214s.

Four Runs with Minimum Logging

What is logged at sender side?? --- the first 2 acked packets for each pstream

Then recover the sendgaps according to the first 2 sendgaps. And recover receive gaps from the timestamp fields in acknowledgements from dag trace file.

Throughput is changed little. Rapid avoid massive losses compared with TCP.

10rates 1us 21 loss
10rates 0us 0  loss
6rates  1us 16 loss
6rates  0us 0  loss
TCP         333 loss,  160 udp loss

CDF of ABests -- in the REAL experiments

ABests in terms of pid

10rates 1us

pid= 641 before packet loss 697Mbps

pid= 643 before packet loss 719Mbps

10rates 0us


6rates 1us

pid= 1181 before packet loss 740Mbps

pid= 1274 before packet loss 710Mbps

10rates 0us
6rates 0us