From: Dave Taht <dave.taht@gmail.com>
To: "George B." <georgeb@gmail.com>, bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] philosophical question
Date: Mon, 30 May 2011 11:05:07 -0600 [thread overview]
Message-ID: <BANLkTikEkbVLViB=BjeCZ-MXvGkjXi_tnQ@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinCzV-x3rZxZ0Fi9b6_zyeU1XVOtg@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1684 bytes --]
On Mon, May 30, 2011 at 9:29 AM, George B. <georgeb@gmail.com> wrote:
> On Mon, May 30, 2011 at 5:25 AM, Dave Taht <dave.taht@gmail.com> wrote:
> >
> >
> > On Sun, May 29, 2011 at 10:24 PM, George B. <georgeb@gmail.com> wrote:
> >>
> >> Ok, say I have a network with no over subscription in my net.
> >
> > I'd love to see one of those. Can I get on it?
>
> Well, we currently have the potential for some microburst oversub
> inside the data center but not too much of it. I can take a 48-port
> GigE switch and have 40G of uplink but the switches aren't fully
> populated yet. Bottlenecks are currently where we might have 25 front
> end servers talking on GigE to a backend server with 20G. So some
> potential for internal microburst oversub but that's beyond the scope
> of this discussion.
>
>
I was serious about asking to get on it. We're trying to get
measurement/test servers in place everywhere we can, so that we can more
deeply analyze the problems the bufferbloat is causing and find more ways to
mitigate it.
As one example, I've been coping with dramatic overbuffering in the GigE
switch we are using on the wndr3700v2s, and working on ways to combat it, as
recent threads on the bloat and bismark-devel lists.
Going SERIOUSLY upstream from a piece of low end consumer gear
to something heavier duty to try and nip this problem in the bud there,
would do much to undo the damage that the change to 1000 deep txqueuelens
did to the world, when GiGE first deployed in the data center about 6 years
ago and then migrated out to consumer gear.
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 2260 bytes --]
next prev parent reply other threads:[~2011-05-30 16:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-30 4:24 George B.
2011-05-30 7:53 ` Neil Davies
2011-05-30 12:25 ` Dave Taht
2011-05-30 15:29 ` George B.
2011-05-30 15:57 ` Jonathan Morton
2011-05-31 17:20 ` George B.
2011-05-31 21:40 ` Juliusz Chroboczek
2011-05-30 17:05 ` Dave Taht [this message]
2011-05-31 18:07 ` Bill Sommerfeld
2011-05-31 19:17 ` Rick Jones
2011-05-31 19:19 ` Jim Gettys
2011-05-31 19:28 ` George B.
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='BANLkTikEkbVLViB=BjeCZ-MXvGkjXi_tnQ@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=georgeb@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