General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Benjamin Cronce <bcronce@gmail.com>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] Bloat done correctly?
Date: Thu, 11 Jun 2015 23:45:15 -0500	[thread overview]
Message-ID: <CAJ_ENFGcAqSTpsVrm2giiRNNrEoJ5ivR_bD6SPsObo29A1s5ng@mail.gmail.com> (raw)

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

This is my first time using a mailing list, so I apologize if I break any
etiquettes.

Here is my situation.
I have 100/100 via GPON, the ISP claims "dedicated" bandwidth defined as
the port is not oversubscribed.
I was told their core network can handle all customers at 100% of their
provisioned speeds, but their
trunk would go down in a spectacular blaze. I was also told their trunk
consists of 6 links to Level 3
and they could handle 5 of those links going down without congestion
occurring on the trunk during peak hours.
The GPON head unit aggregates directly into the core router, router is some
flashy new Cisco
that supports "a lot of 10Gb and 100Gb ports". I have a 1ms hop to my ISP,
then a 9ms hop to Level 3.

The reason I mentioned this is it may be useful when interpreting these
results that the only likely point
of congestion is my 100Mb connection.

DSLReports Jitter test
https://lh3.googleusercontent.com/HxTrRZob4RNU9OdmdRoxS5Ig0xf-9qwZhFwh67uyVPg=w389-h540-no


On to bufferbloat.

Bypass firewall(PFSense) - no AQM/QoS on my part

32/16
http://www.dslreports.com/speedtest/624054

24/12
http://www.dslreports.com/speedtest/624060

Single Stream restriction
http://www.dslreports.com/speedtest/624065


Through the firewall. No other traffic, so HFSC does not matter
80/443/8080 go into the same queue and uses just regular CoDel.
DSLReports uses a "web ping", so the ping goes through the same queue as
the speedtest
http://www.dslreports.com/speedtest/624075

Under load while doing P2P(About 80Mb down and 20Mb up just as I started
the test)
HFSC: P2P in 20% queue and 80/443/8080 in 40% queue with ACKs going to a
20% realtime queue
http://www.dslreports.com/speedtest/622452

Here you can see my quality graph spiked during the tests when I was
outside the firewall.
Because I bypassed the firewall and was no longer being traffic shaped, I
was able to overload the connection.

https://lh3.googleusercontent.com/V4mpd_EMNXCIpdjMGQKbgrYjT_Kts9iIuFR5PnH_5Po=w760-h420-no

To me it seems like bufferbloat is mostly handled. I did send them some
emails to see if I could get a response
on what they use, but no luck.

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

             reply	other threads:[~2015-06-12  4:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-12  4:45 Benjamin Cronce [this message]
2015-06-12  9:08 ` Sebastian Moeller
2015-06-12 15:33   ` Benjamin Cronce
2015-06-12 17:51     ` Sebastian Moeller
2015-06-12 18:44       ` Benjamin Cronce
2015-06-12 18:51   ` Alex Elsayed
2015-06-12 19:14     ` Jonathan Morton
2015-06-12 19:54       ` Sebastian Moeller
2015-06-12 21:19         ` Benjamin Cronce
2015-06-12 19:21     ` Sebastian Moeller
2015-06-12 22:56       ` Alex Elsayed
2015-06-13  7:13         ` Sebastian Moeller

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=CAJ_ENFGcAqSTpsVrm2giiRNNrEoJ5ivR_bD6SPsObo29A1s5ng@mail.gmail.com \
    --to=bcronce@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