From: Dave Taht <dave.taht@gmail.com>
To: Kevin Gross <kevin.gross@avanw.com>
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Jumbo frames and LAN buffers (was: RE: Burst Loss)
Date: Fri, 13 May 2011 14:21:46 -0600 [thread overview]
Message-ID: <BANLkTim0xNx6em7m4A-1nOqu57-J5qumRg@mail.gmail.com> (raw)
In-Reply-To: <-4629065256951087821@unknownmsgid>
[-- Attachment #1: Type: text/plain, Size: 4323 bytes --]
On Fri, May 13, 2011 at 2:03 PM, Kevin Gross <kevin.gross@avanw.com> wrote:
> Do we think that bufferbloat is just a WAN problem? I work on live media
> applications for LANs and campus networks. I'm seeing what I think could be
> characterized as bufferbloat in LAN equipment. The timescales on 1 Gb
> Ethernet are orders of magnitude shorter and the performance problems caused
> are in many cases a bit different but root cause and potential solutions
> are, I'm hoping, very similar.
>
>
>
> Keeping the frame byte size small while the frame time has shrunk maintains
> the overhead at the same level. Again, this has been a conscious decision
> not a stubborn relic. Ethernet improvements have increased bandwidth by
> orders of magnitude. Do we really need to increase it by a couple percentage
> points more by reducing overhead for large payloads?
>
>
>
> The cost of that improved marginal bandwidth efficiency is a 6x increase in
> latency. Many applications would not notice an increase from 12 us to 72 us
> for a Gigabit switch hop. But on a large network it adds up, some
> applications are absolutely that sensitive (transaction processing, cluster
> computing, SANs) and (I thought I'd be preaching to the choir here) there's
> no way to ever recover the lost performance.
>
>
>
You are preaching to the choir here, but I note several things:
Large frame sizes on 10GigE networks to other 10GigE networks is less of a
problem than 10GigE to 10Mbit networks. I would hope/expect that frame would
fragment in that case.
Getting to where latencies are less than 10ms in the general case makes voip
feasible again. I'm still at well over 300ms on bismark.
Enabling higher speed stock market trades and live music exchange over a lan
would be next on my list after getting below 10ms on the local
switch/wireless interface!
A lot of research points to widely enabling some form of fair queuing at the
servers and switches to distribute the load at sane levels. (nagle, 89) I
think few gig+e vendors are doing that in hardware, and it would be good to
know who is and who isn't.
For example, the switch I'm using on bismark has all sorts of wonderful QoS
features such as fair queuing, but as best as I can tell they are not
enabled, and I'm seeing buffering in the switch at well above 20ms....
It is astonishing that a switch chip this capable has reached the consumer
marketplace...
http://realtek.info/pdf/rtl8366s_8366sr_datasheet_vpre-1.4_20071022.pdf
And depressing that so few of it's capabilities have software to configure
them.
> Kevin Gross
>
>
>
> *From:* Dave Taht [mailto:dave.taht@gmail.com]
> *Sent:* Friday, May 13, 2011 8:54 AM
> *To:* rick.jones2@hp.com
> *Cc:* Kevin Gross; bloat@lists.bufferbloat.net
> *Subject:* Re: [Bloat] Burst Loss
>
>
>
>
>
> On Fri, May 13, 2011 at 8:35 AM, Rick Jones <rick.jones2@hp.com> wrote:
>
> On Thu, 2011-05-12 at 23:00 -0600, Kevin Gross wrote:
> > One of the principal reasons jumbo frames have not been standardized
> > is due to latency concerns. I assume this group can appreciate the
> > IEEE holding ground on this.
>
> Thusfar at least, bloaters are fighting to eliminate 10s of milliseconds
> of queuing delay. I don't think this list is worrying about the tens of
> microseconds difference between the transmission time of a 9000 byte
> frame at 1 GbE vs a 1500 byte frame, or the single digit microseconds
> difference at 10 GbE.
>
>
> Heh. With the first iteration of the bismark project I'm trying to get to
> where I have less than 30ms latency under load and have far larger problems
> to worry about than jumbo frames. I'll be lucky to manage 1/10th that
> (300ms) at this point.
>
> Not, incidentally that I mind the idea of jumbo frames. It seems silly to
> be saddled with default frame sizes that made sense in the 70s, and in an
> age where we will be seeing ever more packet encapsulation, reducing the
> header size as a ratio to data size strikes me as a very worthy goal.
>
> _______________________________________________
> Bloat mailing list
> Bloat@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/bloat
>
>
--
Dave Täht
SKYPE: davetaht
US Tel: 1-239-829-5608
http://the-edge.blogspot.com
[-- Attachment #2: Type: text/html, Size: 6678 bytes --]
next prev parent reply other threads:[~2011-05-13 20:13 UTC|newest]
Thread overview: 65+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-26 17:05 [Bloat] Network computing article on bloat Dave Taht
2011-04-26 18:13 ` Dave Hart
2011-04-26 18:17 ` Dave Taht
2011-04-26 18:28 ` dave greenfield
2011-04-26 18:32 ` Wesley Eddy
2011-04-26 19:37 ` Dave Taht
2011-04-26 20:21 ` Wesley Eddy
2011-04-26 20:30 ` Constantine Dovrolis
2011-04-26 21:16 ` Dave Taht
2011-04-27 17:10 ` Bill Sommerfeld
2011-04-27 17:40 ` Wesley Eddy
2011-04-27 7:43 ` Jonathan Morton
2011-04-30 15:56 ` Henrique de Moraes Holschuh
2011-04-30 19:18 ` [Bloat] Goodput fraction w/ AQM vs bufferbloat Richard Scheffenegger
2011-05-05 16:01 ` Jim Gettys
2011-05-05 16:10 ` Stephen Hemminger
2011-05-05 16:30 ` Jim Gettys
2011-05-05 16:49 ` [Bloat] Burst Loss Neil Davies
2011-05-05 18:34 ` Jim Gettys
2011-05-06 11:40 ` Sam Stickland
2011-05-06 11:53 ` Neil Davies
2011-05-08 12:42 ` Richard Scheffenegger
2011-05-09 18:06 ` Rick Jones
2011-05-11 8:53 ` Richard Scheffenegger
2011-05-11 9:53 ` Eric Dumazet
2011-05-12 14:16 ` [Bloat] Publications Richard Scheffenegger
2011-05-12 16:31 ` [Bloat] Burst Loss Fred Baker
2011-05-12 16:41 ` Rick Jones
2011-05-12 17:11 ` Fred Baker
2011-05-13 5:00 ` Kevin Gross
2011-05-13 14:35 ` Rick Jones
2011-05-13 14:54 ` Dave Taht
2011-05-13 20:03 ` [Bloat] Jumbo frames and LAN buffers (was: RE: Burst Loss) Kevin Gross
2011-05-14 20:48 ` Fred Baker
2011-05-15 18:28 ` Jonathan Morton
2011-05-15 20:49 ` Fred Baker
2011-05-16 0:31 ` Jonathan Morton
2011-05-16 7:51 ` Richard Scheffenegger
2011-05-16 9:49 ` Fred Baker
2011-05-16 11:23 ` [Bloat] Jumbo frames and LAN buffers Jim Gettys
2011-05-16 13:15 ` Kevin Gross
2011-05-16 13:22 ` Jim Gettys
2011-05-16 13:42 ` Kevin Gross
2011-05-16 15:23 ` Jim Gettys
[not found] ` <-854731558634984958@unknownmsgid>
2011-05-16 13:45 ` Dave Taht
2011-05-16 18:36 ` Richard Scheffenegger
2011-05-16 18:11 ` [Bloat] Jumbo frames and LAN buffers (was: RE: Burst Loss) Richard Scheffenegger
2011-05-17 7:49 ` BeckW
2011-05-17 14:16 ` Dave Taht
[not found] ` <-4629065256951087821@unknownmsgid>
2011-05-13 20:21 ` Dave Taht [this message]
2011-05-13 22:36 ` Kevin Gross
2011-05-13 22:08 ` [Bloat] Burst Loss david
2011-05-13 19:32 ` Denton Gentry
2011-05-13 20:47 ` Rick Jones
2011-05-06 4:18 ` [Bloat] Goodput fraction w/ AQM vs bufferbloat Fred Baker
2011-05-06 15:14 ` richard
2011-05-06 21:56 ` Fred Baker
2011-05-06 22:10 ` Stephen Hemminger
2011-05-07 16:39 ` Jonathan Morton
2011-05-08 0:15 ` Stephen Hemminger
2011-05-08 3:04 ` Constantine Dovrolis
2011-05-08 13:00 ` Richard Scheffenegger
2011-05-08 12:53 ` Richard Scheffenegger
2011-05-08 12:34 ` Richard Scheffenegger
2011-05-09 3:07 ` Fred Baker
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=BANLkTim0xNx6em7m4A-1nOqu57-J5qumRg@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=bloat@lists.bufferbloat.net \
--cc=kevin.gross@avanw.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