From: Hans-Kristian Bakke <hkbakke@gmail.com>
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] Excessive throttling with fq
Date: Thu, 26 Jan 2017 19:36:47 +0100 [thread overview]
Message-ID: <CAD_cGvG-CvWL9tZ-w8NuctLV=CvahXh0Svkpydk_GmGPcm0wHg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1447 bytes --]
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: 2517 bytes --]
next reply other threads:[~2017-01-26 18:36 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-26 18:36 Hans-Kristian Bakke [this message]
2017-01-26 18:38 ` Hans-Kristian Bakke
2017-01-26 18:55 ` Hans-Kristian Bakke
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_cGvG-CvWL9tZ-w8NuctLV=CvahXh0Svkpydk_GmGPcm0wHg@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