On 2/26/16 3:23 AM, De Schepper, Koen (Nokia - BE) wrote:
> Hi Wes,
>
> Just to let you know that we are still working on AQMs that support scalable
> (L4S) TCPs.
> We could present some of our latest results (if there will be a meeting in
> Buenos Aires, otherwise in Berlin?)
>
> * Performa
On 27/02/2016, Dave Täht wrote:
>
>
>
> On 2/26/16 3:23 AM, De Schepper, Koen (Nokia - BE) wrote:
>> Hi Wes,
>>
>> Just to let you know that we are still working on AQMs that support
>> scalable (L4S) TCPs.
>> We could present some of our latest results (if there will be a meeting in
>> Buenos Air
Alan Jenkins writes:
> I wouldn't complain that I can't sustain 2056Kbps goodput when my fair
> share of the shaped bandwidth is 2000Kbps. The results might be
> showing a significant degradation, or it could be a marginal one that
> pushes over the boundary (between the 2056k and 1427k encodes)
On 28/02/16 13:39, Toke Høiland-Jørgensen wrote:
Alan Jenkins writes:
I wouldn't complain that I can't sustain 2056Kbps goodput when my fair
share of the shaped bandwidth is 2000Kbps. The results might be
showing a significant degradation, or it could be a marginal one that
pushes over the bo
>> Oh, and of course HAS is in itself a hack to work around badly managed
>> queues in the network. In a nicely fairness queued world, we could do
>> away with HAS entirely and just, y'know, stream things at the desired
>> rate...
Perhaps I'm missing something -- how do you to pick the right rate
Alan Jenkins writes:
>> Exactly. And note how they just so happen to pick 11 total flows (10
>> competing, one video) to share the bottleneck, putting the per-flow
>> throughput just below the rate needed to go up one quality level. What a
>> coincidence. At least it shows how difficult it is to
Juliusz Chroboczek writes:
>>> Oh, and of course HAS is in itself a hack to work around badly managed
>>> queues in the network. In a nicely fairness queued world, we could do
>>> away with HAS entirely and just, y'know, stream things at the desired
>>> rate...
>
> Perhaps I'm missing something -
On Sun, Feb 28, 2016 at 5:33 AM, Alan Jenkins
wrote:
> On 27/02/2016, Dave Täht wrote:
>> On 2/26/16 3:23 AM, De Schepper, Koen (Nokia - BE) wrote:
>> I am aware of several unpublished studies. There was also something that
>> compared 1-3 HAS flows from several years back from stanford that I've
> On Feb 27, 2016, at 11:04 AM, Dave Täht wrote:
>
> https://reproducingnetworkresearch.wordpress.com/2014/06/03/cs244-14-confused-timid-and-unstable-picking-a-video-streaming-rate-is-hard/
>
>> o the results are very poor with a particular popular AQM
>
> Define "very poor". ?
Presuming th
On 02/03/16 18:09, Fred Baker (fred) wrote:
On Feb 27, 2016, at 11:04 AM, Dave Täht wrote:
https://reproducingnetworkresearch.wordpress.com/2014/06/03/cs244-14-confused-timid-and-unstable-picking-a-video-streaming-rate-is-hard/
o the results are very poor with a particular popular AQM
Def
> On Mar 2, 2016, at 12:53 PM, Alan Jenkins
> wrote:
>
> Google avoid the bursts you describe, using pacing.
I have been an advocate of pacing during the first transmission burst
(including after an idle period) for quite some time, and also for delay-based
algorithms. There would be no need
11 matches
Mail list logo
