Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Sujith Manoharan <sujith@msujith.org>
To: "David P. Reed" <dpreed@reed.com>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] looking over ampdu stats
Date: Mon, 20 Jan 2014 21:05:02 +0530	[thread overview]
Message-ID: <21213.16934.851675.554642@gargle.gargle.HOWL> (raw)
In-Reply-To: <0045e4e1-f1dd-4e15-81fb-4d616ffab08d@katmail.1gravity.com>

David P. Reed wrote:
> It's worth remembering that while aggregation of data in single units might
> reduce overhead, end to end latency is far more critical to most Internet
> apps.
> 
> Focusing on optimizing throughput for the last few percent in corner cases is
> NOT desirable.  In fact, it is the cause of pervasive buffer bloated designs,
> and the creator of "Daddy broke the Internet" scenarios.
> 
> Since LTE is badly configured in the field for Internet use, causing denial of
> service to many users because of bloated (multisecond to drain) queues, I
> would stop focusing on this, which is only a 10 percent issue.  Multisecond
> bloat is a disaster. You are fiddling while Rome burns imo.

Well, the 10 percent is with a 1x1 card. It becomes worse with 2x2 and with 3x3,
it's really bad - about 180 Mbps when it should be close to 290 Mbps. Using more
parallel threads appears to improve things, but I don't see this behavior with
a windows client, where a single iperf stream gives good results, unlike ath9k.

Sujith

      reply	other threads:[~2014-01-20 15:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-19 17:20 Dave Taht
2014-01-20  3:27 ` Sujith Manoharan
2014-01-20  3:38   ` Dave Taht
2014-01-20  3:55     ` Sujith Manoharan
2014-01-20 15:09       ` David P. Reed
2014-01-20 15:35         ` Sujith Manoharan [this message]

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/cerowrt-devel.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=21213.16934.851675.554642@gargle.gargle.HOWL \
    --to=sujith@msujith.org \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=dpreed@reed.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