From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] bloat at gigE
Date: Wed, 23 Sep 2015 14:22:44 +0200 [thread overview]
Message-ID: <20150923122244.GA12149@sesse.net> (raw)
In-Reply-To: <CAJ_ENFG1KrJzSjzNY=7yX+F0SeJB1M7j9bV5yp_pcga_TbKgmw@mail.gmail.com>
On Wed, Sep 23, 2015 at 07:10:33AM -0500, Benjamin Cronce wrote:
> The upload wasn't even saturated. Probably why upload bloat was very low.
> Large bloat on the download just shows you the server really can push more
> than 1Gb. 200ms bloat with 913Mb down is about 20MiB of buffer. That's
> insane! That's about 20x more buffer than my entire 24 port 1Gb Procurve
> managed switch. What kind of network equipment has that much buffer?
When I ran the bufferbloat test last time, I got pretty much exactly 250 ms
bloat at 1 GigE. That's ~30 MB. The equipment at the other end (where I
suppose the bloat was) was a Juniper MX960.
/* Steinar */
--
Homepage: http://www.sesse.net/
next prev parent reply other threads:[~2015-09-23 12:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-23 8:34 Dave Taht
2015-09-23 12:10 ` Benjamin Cronce
2015-09-23 12:22 ` Steinar H. Gunderson [this message]
2015-09-23 12:23 ` Mikael Abrahamsson
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=20150923122244.GA12149@sesse.net \
--to=sgunderson@bigfoot.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