From: Dave Taht <dave.taht@gmail.com>
To: ECN-Sane <ecn-sane@lists.bufferbloat.net>
Subject: [Ecn-sane] bittorrent & ecn
Date: Sun, 15 Dec 2019 06:56:26 -0800 [thread overview]
Message-ID: <CAA93jw6ccfisQa0cDsy+3D_z-16+dYyATLLQAQe_J4xydoDR4w@mail.gmail.com> (raw)
I was kind of wondering if ecn would be used by bittorrent clients and
servers. (it's not supported by utp, I think, but when you use tcp, it
uses default tcp options) So I loaded up (FOR SCIENCE!) 100+ common
torrents with no limits on connections with an inbound fq_codel based
shaper in place and ecn enabled on the torrent client.
Yep. ecn gets used. How many torrent servers negotiate it? How many
clients? (I imagine the entire apple universe does now)
qdisc fq_codel 130: parent 1:13 limit 1001p flows 1024 quantum 300
target 5.0ms interval 100.0ms ecn
Sent 669116971742 bytes 525750376 pkt (dropped 750412, overlimits 0 requeues 0)
backlog 288139b 201p requeues 0
maxpacket 1514 drop_overlimit 1047 new_flow_count 65837164 ecn_mark 70963
new_flows_len 0 old_flows_len 73
sleep 60
qdisc fq_codel 130: parent 1:13 limit 1001p flows 1024 quantum 300
target 5.0ms interval 100.0ms ecn
Sent 671021262523 bytes 527225759 pkt (dropped 792750, overlimits 0 requeues 0)
backlog 46605b 39p requeues 0
maxpacket 1514 drop_overlimit 1047 new_flow_count 66286036 ecn_mark 74965
new_flows_len 0 old_flows_len 29
Remarkably my connection stayed pretty darn usable. In fact, I hardly
noticed. My streaming radio glitched once. Web was fine, but gmail
took a while longer to load all the resources. Taking a packet capture
now.
This is theoretically the most expensive bit of research I've ever
done for the bufferbloat project, in a matter of hours I'll have
violated copyright ~800 times, which is about 200m dollars at 250k
per.
Folk are encouraged to use vpns for torrents nowadays, but I can't see
how that would work with libutp and a max rtt of 100ms before it
starts to back off. I guess I'll look at that next.
Dear RIAA: I promise to delete the files when I'm done, and I'm only
capturing headers on the capture. I'd rather someone with the
protection of a major university followup on this line of research....
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
next reply other threads:[~2019-12-15 14:56 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-15 14:56 Dave Taht [this message]
2019-12-15 23:09 ` Dave Taht
2019-12-16 7:09 ` Sebastian Moeller
2019-12-16 7:43 ` Dave Taht
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/ecn-sane.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAA93jw6ccfisQa0cDsy+3D_z-16+dYyATLLQAQe_J4xydoDR4w@mail.gmail.com \
--to=dave.taht@gmail.com \
--cc=ecn-sane@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