Opened 6 years ago

Closed 6 years ago

#979 closed enhancement (fixed)

Use actual initial RTT value in streaming

Reported by: Zlatin Balevsky Owned by: Zlatin Balevsky
Priority: minor Milestone: 0.9.8
Component: streaming Version: 0.9.6
Keywords: rtt rto Cc: zab@…
Parent Tickets: Sensitive: no

Description

backround: http://sgros.blogspot.com/2012/02/calculating-tcp-rto.html

<zab> the formulas are the same as tcp, but does tcp start off with some initial values?
<zab> I found them (on the same page I posted) tcp.initial_rto - 1 sec
<zab> no initial values for rtt or rttdev
<zab> our initial rto = 12 sec, initial rtt = 8 sec
<zab> rttdev = 4000
<zzz> see stats stream.con.initialRTT.{in,out}
<zzz> cant remember how in is calculated.
<zab> the calculation is the same one as tcp; the only difference is that tcp does not have an initial value for rtt and rttdev
<zzz> my stats are 3400 ms in, 4300 ms out
<zzz> either lowering initial RTT or using actual RTT sounds like a good idea - wherever the stats are set would be the place to call setRTT()

Subtickets

Change History (3)

comment:1 Changed 6 years ago by Zlatin Balevsky

Work going on in i2p.i2p.979 branch

comment:2 Changed 6 years ago by Zlatin Balevsky

Documentation changes in branch i2p.www.979

comment:3 Changed 6 years ago by Zlatin Balevsky

Milestone: 0.9.8
Resolution: fixed
Status: newclosed

Should be merged with revision fa509893effa9445a0833115160aed8fe6fed268
Documentation updated with revision 4ecf70e5be8f493e33debb8c39856d7ff213bdae
router version 0.9.7-1

Note: See TracTickets for help on using tickets.