General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Hans-Kristian Bakke <hkbakke@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Excessive throttling with fq
Date: Thu, 26 Jan 2017 19:55:18 +0100	[thread overview]
Message-ID: <CAD_cGvFmNm-EnVztd2i2Q8dxeV+Av_mPO6sLte8KqiMgQgBU=Q@mail.gmail.com> (raw)
In-Reply-To: <CAD_cGvHhmBDjt4gFYRHBELyAKEXeH4AycRFjH4bcWCC7RAbacw@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 2346 bytes --]

After some more testing I see that if I disable fq pacing the performance
is restored to the expected levels:
# for i in eth0 eth1; do tc qdisc replace dev $i root fq nopacing; done

Is this expected behaviour? There is some background traffic, but only in
the sub 100 mbit/s on the switches and gateway between the server and
client.

The chain:
Windows 10 client -> 1000 mbit/s -> switch -> 2xgigabit LACP -> switch -> 4
x gigabit LACP -> gw (fq_codel on all nics) -> 4 x gigabit LACP (the same
as in) -> switch -> 2 x lacp -> server (with misbehaving fq pacing)


On 26 January 2017 at 19:38, Hans-Kristian Bakke <hkbakke@gmail.com> wrote:

> I can add that this is without BBR, just plain old kernel 4.8 cubic.
>
> On 26 January 2017 at 19:36, Hans-Kristian Bakke <hkbakke@gmail.com>
> wrote:
>
>> Another day, another fq issue (or user error).
>>
>> I try to do the seeminlig simple task of downloading a single large file
>> over local gigabit  LAN from a physical server running kernel 4.8 and
>> sch_fq on intel server NICs.
>>
>> For some reason it wouldn't go past around 25 MB/s. After having replaced
>> SSL with no SSL, replaced apache with nginx and verified that there is
>> plenty of bandwith available between my client and the server I tried to
>> change qdisc from fq to pfifo_fast. It instantly shot up to around the
>> expected 85-90 MB/s. The same happened with fq_codel in place of fq.
>>
>> I then checked the statistics for fq and the throttled counter is
>> increasing massively every second (eth0 and eth1 is LACPed using Linux
>> bonding so both is seen here):
>>
>> qdisc fq 8007: root refcnt 2 limit 10000p flow_limit 100p buckets 1024
>> orphan_mask 1023 quantum 3028 initial_quantum 15140 refill_delay 40.0ms
>>  Sent 787131797 bytes 520082 pkt (dropped 15, overlimits 0 requeues 0)
>>  backlog 98410b 65p requeues 0
>>   15 flows (14 inactive, 1 throttled)
>>   0 gc, 2 highprio, 259920 throttled, 15 flows_plimit
>> qdisc fq 8008: root refcnt 2 limit 10000p flow_limit 100p buckets 1024
>> orphan_mask 1023 quantum 3028 initial_quantum 15140 refill_delay 40.0ms
>>  Sent 2533167 bytes 6731 pkt (dropped 0, overlimits 0 requeues 0)
>>  backlog 0b 0p requeues 0
>>   24 flows (24 inactive, 0 throttled)
>>   0 gc, 2 highprio, 397 throttled
>>
>> Do you have any suggestions?
>>
>> Regards,
>> Hans-Kristian
>>
>
>

[-- Attachment #2: Type: text/html, Size: 4625 bytes --]

  reply	other threads:[~2017-01-26 18:55 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26 18:36 Hans-Kristian Bakke
2017-01-26 18:38 ` Hans-Kristian Bakke
2017-01-26 18:55   ` Hans-Kristian Bakke [this message]
2017-01-26 19:18     ` Eric Dumazet
2017-01-26 19:58       ` David Lang
2017-01-26 20:19         ` Hans-Kristian Bakke
2017-01-26 20:41           ` Eric Dumazet
2017-01-26 20:46             ` Hans-Kristian Bakke
2017-01-26 21:00               ` Eric Dumazet
     [not found]                 ` <CAD_cGvFXR+Qb9_gnp=k4UttJZnrRRm4i19of7D4v8MK9EjeZ6Q@mail.gmail.com>
2017-01-26 21:07                   ` Eric Dumazet
     [not found]                     ` <CAD_cGvGuCU+R=ddTGTnLF3C8avmJ=UZyAYAkD0FQzd-v6fknPw@mail.gmail.com>
2017-01-26 21:33                       ` Eric Dumazet
2017-01-26 20:54           ` Eric Dumazet
2017-01-26 20:57             ` Hans-Kristian Bakke
2020-02-19  6:58               ` Alexey Ivanov
2020-02-19 13:52                 ` Neal Cardwell

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAD_cGvFmNm-EnVztd2i2Q8dxeV+Av_mPO6sLte8KqiMgQgBU=Q@mail.gmail.com' \
    --to=hkbakke@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox