Fred thinking on this more the 'g' (the function of RTT) is something like 'min' - on the assumption that the path doesn't change during the transfer - that represents the immutable part of the end-to-end delay, the 'inflight' buffering.
Neil On 7 Apr 2012, at 16:25, Dave Taht wrote: > The test HD tcp stream is up at > > http://cesur.tg12.gathering.org:9094/ > > on both ipv6 and ipv4. They are streaming anywhere up to 1000 users, > and there is an astounding amount of ipv6 present - 73% of the room > has an ipv6 address. > > I took some captures from california last night, they were > interesting. I think a few more captures would also be interesting. > > One indicated throttling at the isp at t+60 seconds, the others showed > stuff dropping out for large periods of time. (170ms rtt here!) > > I'd like to look into what percentage of the failures I observed > happened on the wifi hop vs the ethernet gateway > since then many changes where made, and I'm low on sleep. (what do > geeks do on a friday night?) > > I don't know if they are still trying sfqred or qfq in production - > they worked! - but had little effect (as is to be kind of expected > with the instantaneous queue length being so short and bandwidth so > high on their first and nearest hops....) > On Sat, Apr 7, 2012 at 8:08 AM, Eric Dumazet <[email protected]> wrote: >> Le samedi 07 avril 2012 à 00:21 +0200, Steinar H. Gunderson a écrit : >> >>> I'll be perfectly happy just doing _something_; I don't need a perfect >>> solution. We have one more night of streaming, and then the event is over. >>> :-) > > > -- > Dave Täht > SKYPE: davetaht > US Tel: 1-239-829-5608 > http://www.bufferbloat.net > _______________________________________________ > Bloat mailing list > [email protected] > https://lists.bufferbloat.net/listinfo/bloat _______________________________________________ Bloat mailing list [email protected] https://lists.bufferbloat.net/listinfo/bloat
