General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: d@taht.net (Dave Täht)
To: bloat <bloat@lists.bufferbloat.net>
Subject: [Bloat] TCP vegas vs TCP cubic
Date: Wed, 02 Feb 2011 08:20:35 -0700	[thread overview]
Message-ID: <87bp2upinw.fsf@cruithne.co.teklibre.org> (raw)


On a suggestion from one of the posters to jg's blog, I took a look at
tcp vegas. The results I got were puzzling. 

With tcp cubic, I typically get 71Mbit/sec and all the side effects of
bufferbloat with a single stream.

With vegas turned on, a single stream peaks at around 20Mbit.

10 vegas streams did about 55Mbit in total. 

Can I surmise that TCP cubic is like a dragster, able to go really fast
in one direction down a straightaway, and TCP vegas more like an 80s
model MR2, maneuverable, but underpowered?

The testbed network: http://nex-6.taht.net/images/housenet.png 
The test path: laptop->nano-m->nano-m->openrd 
    (I note that this path almost never exhibits packet loss) 

Most of the machines on the path are running with
minimal txqueues and dma buffers running as low as they can go.

The tests:


With cubic:

$ openrd: iperf -s 
$ laptop: iperf -t 60 -c openrd

With vegas (on both laptop and server)
modprobe tcp_vegas
echo vegas > /proc/sys/net/ipv4/tcp_congestion_control

openrd:$ iperf -s 
laptop:$ iperf -t 60 -c openrd &
laptop:$ ping  

On a failed hunch, I also re-ran the tests with a much larger 
congestion window:

echo /proc/sys/net/core/rmem_max  
echo /proc/sys/net/core/wmem_max  

iperf -w8m -s

To no net difference in effect.

-- 
Dave Taht
http://nex-6.taht.net

             reply	other threads:[~2011-02-02 15:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-02 15:20 Dave Täht [this message]
2011-02-02 16:05 ` Justin McCann
2011-02-02 16:29   ` Dave Täht
2011-02-02 18:37     ` Richard Scheffenegger
2011-02-02 19:16       ` Dave Täht
2011-02-02 20:01         ` Jim Gettys
2011-02-03 18:34           ` Seth Teller
2011-02-02 21:36         ` Richard Scheffenegger
2011-02-03 17:53   ` Dave Taht
2011-02-04  9:51     ` Juliusz Chroboczek
2011-02-04 15:18       ` Dave Täht

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=87bp2upinw.fsf@cruithne.co.teklibre.org \
    --to=d@taht.net \
    --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