General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Benjamin Cronce <bcronce@gmail.com>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] tackling torrent on a 10mbit uplink (100mbit down)
Date: Fri, 19 Jun 2015 18:08:34 -0700	[thread overview]
Message-ID: <CAA93jw4Zgjc+_MFzQK62M7PC2iun2U_u81U9mE61+mUfQK-7Vg@mail.gmail.com> (raw)
In-Reply-To: <CAJ_ENFHMnu-d-fbqBDUNwFfn+0xLhLP=-ZaSk+n0NqnD9+-3Xw@mail.gmail.com>

On Fri, Jun 19, 2015 at 3:14 PM, Benjamin Cronce <bcronce@gmail.com> wrote:

> Linux ISOs are a great way to saturate your download. I have enough
> downloaded that while seeding, I can sustain over 10Mb/s, but don't expect
> to saturate your upload since they're already heavily seeded, but less so
> since I stopped recently.

I went for a representative sample of what torrent gets used for by
ordinary users, randomly picking 4 torrents in the top 10 of music,
tv, movies, and... um, er, ah, pr0n.

...FOR SCIENCE! :)

Going for a linux distro would have yielded a different result. I used
the gutenberg torrent and linux distros primarily in those earlier
tests years ago, and I felt that the data I got then was probably
skewed by that towards linux's behaviors.

The major difference between then and now was no tcp whatsoever, and
no ipv6, where before I had seen a lot of tcp and ipv6. I can redo
those tests at some future point. I think the tcp absence here was
partially upnp not working correctly in my setup last night. I have
been quite concerned that as IW10 moved out there generically that
that would be bad.... and perhaps the lack of ipv6 was due to the
flooding ipv6 issue I posted earlier.

So I'll think about how to go about it properly harder... after I
patch transmission to tos mark packets correctly... (my original
intent was to watch cake do classification) but I would argue to do it
fairly right, consistently, over time, while altering other major
variables like qdisc, would be to continue pulling from the top 10
categories the public is pulling from.

suggestions, anyone?

-- 
Dave Täht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast

  reply	other threads:[~2015-06-20  1:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-19 16:01 Dave Taht
2015-06-19 22:14 ` Benjamin Cronce
2015-06-20  1:08   ` Dave Taht [this message]
2015-06-20  0:47 ` Dave Taht
2015-06-21 15:39   ` Juliusz Chroboczek
2015-06-21 16:24     ` Benjamin Cronce
2015-06-21 15:32 ` [Bloat] BitTorrent and IPv6 [was: tackling torrent...] Juliusz Chroboczek
2015-06-22 19:29   ` Dave Taht
2015-06-22 21:08     ` Juliusz Chroboczek
2015-06-24 17:30       ` Juliusz Chroboczek

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=CAA93jw4Zgjc+_MFzQK62M7PC2iun2U_u81U9mE61+mUfQK-7Vg@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=bcronce@gmail.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