On 21 Mar, 2011, at 12:18 am, da...@lang.hm wrote:
0) Buffering more than 1 second of data is always unacceptable.
what about satellite links? my understanding is that the four round trips to
geosync orbit (request up, down, reply up down) result in approximatly 1 sec
round trip.
That
On 03/21/2011 09:50, Dave Täht wrote:
[..]
We're not testing interplanetary networks here, (rather, an artificially
induced one extending out well beyond the moon!) but it bears a little
thinking about.
Perhaps an idea for presenting bufferbloat visually? Draw a picture of the
space
On 21 Mar, 2011, at 12:50 am, Dave Täht wrote:
0) Buffering more than 1 second of data is always unacceptable.
Well, in the case of the DTN, it's required.
We're not testing interplanetary networks here, (rather, an artificially
induced one extending out well beyond the moon!) but it
Instead of dribs and drabs. I don't know when the test started, but this
took a very long time.
Server responding, beginning test...
MinRTT: 1.1ms
Scenario 1: 0 uploads, 1 downloads... 8024 KiB/s down, 12.71 Hz smoothness
Scenario 2: 1 uploads, 0 downloads... 6526 KiB/s up, 5.52 Hz smoothness
On 3/20/2011 9:28 PM, da...@lang.hm wrote:
On Mon, 21 Mar 2011, Jonathan Morton wrote:
On 21 Mar, 2011, at 12:18 am, da...@lang.hm wrote:
0) Buffering more than 1 second of data is always unacceptable.
what about satellite links? my understanding is that the four round
trips to geosync
