General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dan Siemon <dan@coverfire.com>
To: bloat@lists.bufferbloat.net
Subject: [Bloat] Network latency experiments
Date: Mon, 21 Feb 2011 18:27:04 -0500	[thread overview]
Message-ID: <1298330824.4443.17.camel@ganymede.coverfire.com> (raw)

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

I spent some time over the weekend playing around with different network
configurations and collecting latency results. Hopefully this is
interesting to the people on this list.

http://www.coverfire.com/archives/2011/02/21/network-latency-experiments/

Experiments
1) Linux defaults
2) Reduce buffers
3) Reduce buffers + SFB
4) Reduce buffers + SFQ

Each was tested under upstream load, downstream load and bidirectional
load.

[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

             reply	other threads:[~2011-02-21 23:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-21 23:27 Dan Siemon [this message]
2011-02-22  9:26 ` Florian Lohoff
2011-02-25 20:47   ` Jesper Dangaard Brouer

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=1298330824.4443.17.camel@ganymede.coverfire.com \
    --to=dan@coverfire.com \
    --cc=bloat@lists.bufferbloat.net \
    /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