General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Michael Richardson <mcr@sandelman.ca>
To: mallman@icir.org
Cc: bloat@lists.bufferbloat.net
Subject: Re: [Bloat] Bufferbloat Paper
Date: Wed, 09 Jan 2013 15:14:02 -0500	[thread overview]
Message-ID: <5864.1357762442@sandelman.ca> (raw)
In-Reply-To: <20130108135510.EF4CA59F9BA@lawyers.icir.org>

[-- Attachment #1: Type: text/plain, Size: 1658 bytes --]


>>>>> "Mark" == Mark Allman <mallman@icir.org> writes:
    Mark> less than 1Gbps, but I forget the actual wireless technology used on
    Mark> the IHR).  The IHRs are all run into a switch (SW) at 1Gbps.  The
    Mark> switch connects to the Internet via a 1Gbps link (so, this is a
    Mark> theoretical bottleneck right here ...).  The "REH" is the remote end
    Mark> host.  We monitor via mirroring on SW.

1) do you max out your 1Gb/s uplink at all?
2) have you investigated bufferbloat on that port of the switch?
   (and do you have congestion issues on your mirror port?
   I guess that the point of the loss analysis...)

    Mark> (3) This data is not ideal.  Ideally I'd like to directly
    Mark> measure queues 
    Mark> in a bazillion places.  That'd be fabulous.  But, I am working with
    Mark> what I have.  I have traces that offer windows into the actual queue
    Mark> occupancy when the local users I monitor engage particular remote
    Mark> endpoints.  Is this representative of the delays I'd find when the
    Mark> local users are not engaging the remote end system?  I have no
    Mark> idea.  I'd certainly like to know.  But, the data doesn't tell me.
    Mark> I am reporting what I have.  It is something.  And, it is more than
    Mark> I have seen reported anywhere else.  Folks should go collect more
    Mark> data.

Thank you for this.

-- 
]               Never tell me the odds!                 | ipv6 mesh networks [ 
]   Michael Richardson, Sandelman Software Works        | network architect  [ 
]     mcr@sandelman.ca  http://www.sandelman.ca/        |   ruby on rails    [ 
	

[-- Attachment #2: Type: application/pgp-signature, Size: 307 bytes --]

  parent reply	other threads:[~2013-01-09 20:14 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07 23:37 Hagen Paul Pfeifer
2013-01-08  0:33 ` Dave Taht
2013-01-08  0:40   ` David Lang
2013-01-08  2:04   ` Mark Watson
2013-01-08  2:24     ` David Lang
2013-01-09 20:08       ` Michael Richardson
2013-01-08  4:52     ` Mark Watson
2013-01-08  1:54 ` Stephen Hemminger
2013-01-08  2:15   ` Oliver Hohlfeld
2013-01-08 12:44   ` Toke Høiland-Jørgensen
2013-01-08 13:55     ` Mark Allman
2013-01-09  0:03       ` David Lang
2013-01-10 13:01         ` Mark Allman
2013-01-09 20:14       ` Michael Richardson [this message]
2013-01-09 20:19         ` Mark Allman
2013-01-09 20:31           ` Michael Richardson
2013-01-10 18:05             ` Mark Allman
2013-01-08 14:04     ` Mark Allman
2013-01-08 17:22   ` Dave Taht
2013-01-09 20:05 ` Michael Richardson
2013-01-09 20:14   ` Mark Allman
2013-01-08  7:35 [Bloat] bufferbloat paper Ingemar Johansson S
2013-01-18 22:00 ` Haiqing Jiang
2013-01-08 19:03 Hal Murray
2013-01-08 20:28 ` Jonathan Morton
2013-01-09  0:12 ` David Lang
2013-01-09  1:59   ` Mark Allman
2013-01-09  4:53     ` David Lang
2013-01-09  5:13       ` Jonathan Morton
2013-01-09  5:32       ` Mark Allman
     [not found] <87r4lvgss4.fsf@toke.dk>
2013-01-09  3:39 ` [Bloat] Bufferbloat Paper Mark Allman
2013-01-09  5:02   ` David Lang
2013-01-18  1:23     ` grenville armitage

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=5864.1357762442@sandelman.ca \
    --to=mcr@sandelman.ca \
    --cc=bloat@lists.bufferbloat.net \
    --cc=mallman@icir.org \
    /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