From: Benjamin Cronce <bcronce@gmail.com>
To: Dave Taht <dave.taht@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] bloat at gigE
Date: Wed, 23 Sep 2015 07:10:33 -0500 [thread overview]
Message-ID: <CAJ_ENFG1KrJzSjzNY=7yX+F0SeJB1M7j9bV5yp_pcga_TbKgmw@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw5tzTFubRWvymhMJ6YZmuNHqO7gJYaOxeBbVwH68dYdMw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 844 bytes --]
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?
On Wed, Sep 23, 2015 at 3:34 AM, Dave Taht <dave.taht@gmail.com> wrote:
> I have been enjoying the more unusual bloat results, and where they
> come from. Here's a cool one.
>
> http://www.dslreports.com/speedtest/1424935
>
> --
> Dave Täht
> endo is a terrible disease: http://www.gofundme.com/SummerVsEndo
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
[-- Attachment #2: Type: text/html, Size: 1542 bytes --]
next prev parent reply other threads:[~2015-09-23 12:10 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 [this message]
2015-09-23 12:22 ` Steinar H. Gunderson
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='CAJ_ENFG1KrJzSjzNY=7yX+F0SeJB1M7j9bV5yp_pcga_TbKgmw@mail.gmail.com' \
--to=bcronce@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=dave.taht@gmail.com \
/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