so you’re at the mercy of TCP
>>> receive windows and latency limiting how fast you can go on that single
>>> stream.
>>>
>>>
>>>
>>> *From:* Bloat [mailto:bloat-boun...@lists.bufferbloat.net] *On Behalf
>>> Of *Aaron Wood
>>> *Sent:* Tue
On Thu, 21 Sep 2017, Toke Høiland-Jørgensen wrote:
It would be interesting if we could run some netperf tests using port
80/443 for the listening socket for the data connection (although if
doing deep-packet inspection, we might need to use an actual HTTP
transfer).
Trouble with this is that
t [mailto:bloat-boun...@lists.bufferbloat.net] *On Behalf Of
>> *Aaron Wood
>> *Sent:* Tuesday, August 29, 2017 11:16 PM
>> *To:* bloat <bloat@lists.bufferbloat.net>
>> *Subject:* [Bloat] different speeds on different ports? (benchmarking
>> fun)
>>
&g
-boun...@lists.bufferbloat.net] *On Behalf Of
> *Aaron
> Wood
> *Sent:* Tuesday, August 29, 2017 11:16 PM
> *To:* bloat <bloat@lists.bufferbloat.net>
> *Subject:* [Bloat] different speeds on different ports? (benchmarking fun)
>
>
>
> I don't have a full writeup yet, b
...@lists.bufferbloat.net] On Behalf Of Aaron Wood
Sent: Tuesday, August 29, 2017 11:16 PM
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] different speeds on different ports? (benchmarking fun)
I don't have a full writeup yet, but wanted to ask if people on here have run
into this.
I'm seeing a dis
Hi Toke, Stefan, Aaron,
> On Sep 21, 2017, at 13:16, Toke Høiland-Jørgensen wrote:
>
>> It would be interesting if we could run some netperf tests using port
>> 80/443 for the listening socket for the data connection (although if
>> doing deep-packet inspection, we might need to
> It would be interesting if we could run some netperf tests using port
> 80/443 for the listening socket for the data connection (although if
> doing deep-packet inspection, we might need to use an actual HTTP
> transfer).
Trouble with this is that netserver would have to run as root to be able
On 2017-08-30 07:15, Aaron Wood wrote:
The current hypothesis that we have is that this is due to either
traffic class, or the ports that traffic are running on. I've ruled
out the ping streams, as a parallel set of netperf tcp_maerts
downloads has the same 120Mbps roof.
Also think of
A packet capture from dslreports might be useful also.
___
Bloat mailing list
Bloat@lists.bufferbloat.net
https://lists.bufferbloat.net/listinfo/bloat