Also, it is easier (for me at least) to download a tarball of all your
results for a given run, rather than each one individually.
I am thinking we can rename ack-filter-aggressive to
ack-filter-too-damn-aggressive.
Dave Taht writes:
> I just want to verify that you increased
Georgios Amanakis writes:
> Results with irtt/flent-git. Same setup as before:
Looks like that is still using netperf for the UDP measurements. Flent
does some sanity checks on irtt before using it, which may be failing.
Running flent with -v should give some hints...
On Wed, Nov 29, 2017 at 5:24 PM Georgios Amanakis
wrote:
> I just installed flent-git (thanks for the aur) and irtt, was more
> straightforward than I expected :)
> In my setup netserver runs on server, flent runs on client. Where should I
> run irtt server?
>
irtt server
Georgios Amanakis writes:
> @Pete @Toke just saw your responses. Thank you very much for the
> explanation. I will give irtt and flent-git a try, and maybe build an
> aur package for archlinux.
There's already an AUR package for flent-git; haven't gotten around to
making
@Pete @Toke just saw your responses. Thank you very much for the
explanation. I will give irtt and flent-git a try, and maybe build an aur
package for archlinux.
George
On Wed, Nov 29, 2017 at 11:08 AM, Pete Heist wrote:
>
> > On Nov 29, 2017, at 4:44 PM, Toke
> On Nov 29, 2017, at 4:44 PM, Toke Høiland-Jørgensen wrote:
>
>> (That was also informative for me about how netperf decides when to
>> emit a data point…)
>
> In that case I can add that the stated reason for this way of doing
> things is performance (i.e., emitting data points
I did some more testing. Same setup as before, I varied the amount of delay:
server--delay--mbox--client
netserver Xms/Xms 45/900mbit
Cake config:
qdisc cake 801b: dev mbox.l root refcnt 2 bandwidth 45Mbit diffserv3
> (That was also informative for me about how netperf decides when to
> emit a data point…)
In that case I can add that the stated reason for this way of doing
things is performance (i.e., emitting data points should not interfere
with transfer performance). This is mostly an issue on systems
> On Nov 29, 2017, at 3:50 PM, Toke Høiland-Jørgensen wrote:
>
> Georgios Amanakis > writes:
>
>> I am troubled by the number of data points flent reports for some pings and
>> uploads in this setup. A typical ack-filter result,
Georgios Amanakis writes:
> I am troubled by the number of data points flent reports for some pings and
> uploads in this setup. A typical ack-filter result, similar to rrul2 I
> posted before, looks like this:
> Summary of rrul test run 'rrul_cakeeth_ds3_900mbit_45mbit_ack'
I am troubled by the number of data points flent reports for some pings and
uploads in this setup. A typical ack-filter result, similar to rrul2 I
posted before, looks like this:
Summary of rrul test run 'rrul_cakeeth_ds3_900mbit_45mbit_ack' (at
2017-11-29 14:37:5
5.719180):
With ack-filter-aggressive I get results similar to rrul1 in ~10% of the
runs, 90% are similar to rrul2.
With ack-filter I haven't managed yet to get a rrul1 result, all of them
are similar to rrul2.
Will experiment more today.
George
On Tue, Nov 28, 2017 at 11:01 PM, Dave Taht
> On Nov 29, 2017, at 9:19 AM, Pete Heist wrote:
>
>> On Nov 29, 2017, at 4:42 AM, Georgios Amanakis wrote:
>>
>> @Pete I think you need to start netserver on the client first (in your case,
>> you are running flent on the server): "ip netns exec
@Pete I think you need to start netserver on the client first (in your
case, you are running flent on the server): "ip netns exec client netserver"
On Tue, Nov 28, 2017 at 7:16 PM, Pete Heist wrote:
>
> > On Nov 28, 2017, at 11:52 PM, Dave Taht wrote:
> >
>
> On Nov 28, 2017, at 11:52 PM, Dave Taht wrote:
>
> A diffserv 200Mbit result would be good.
>
> We are utterly out of cpu at 900mbits here.
>
>
Wow, I see flent’s combination plots are handy though.
Stuff to sort in irtt also. Merely setting the source IP of an outgoing
Pete Heist writes:
>> On Nov 28, 2017, at 8:07 PM, Dave Taht wrote:
>>
>> Pete Heist writes:
>>
>>> *** Round 3 Plans:
>>>
>>> * Use netem to test a spread of simulated rtts and bandwidths.
>>
>> Since you are leveraging a few too
> On Nov 28, 2017, at 8:07 PM, Dave Taht wrote:
>
> Pete Heist writes:
>
>> *** Round 3 Plans:
>>
>> * Use netem to test a spread of simulated rtts and bandwidths.
>
> Since you are leveraging a few too few boxes, attached are my current
> scripts for
Pete Heist writes:
>
> *** Round 3 Plans:
>
> * Use netem to test a spread of simulated rtts and bandwidths.
Since you are leveraging a few too few boxes, attached are my current
scripts for fiddling a bit with network namespaces. I added individual
ssh, irtt, etc, servers
> On Nov 28, 2017, at 3:11 PM, Pete Heist wrote:
>
> * still don’t think I managed to get udp flood to work, must be doing
> something wrong:
>
> http://www.drhleny.cz/bufferbloat/cake/round2/udpflood_eg_fq_codel_900mbit/index.html
>
>
19 matches
Mail list logo