Re: [ledbat] Note well on the BitTorrent problem on the example...
Nicholas Weaver <nweaver@ICSI.Berkeley.EDU> Sun, 23 November 2008 16:12 UTC
Return-Path: <ledbat-bounces@ietf.org>
X-Original-To: tana-archive@ietf.org
Delivered-To: ietfarch-tana-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 980463A6837; Sun, 23 Nov 2008 08:12:57 -0800 (PST)
X-Original-To: ledbat@core3.amsl.com
Delivered-To: ledbat@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 9F10B3A6837 for <ledbat@core3.amsl.com>; Sun, 23 Nov 2008 08:12:55 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.599
X-Spam-Level:
X-Spam-Status: No, score=-6.599 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id CJlm6t4e+jU7 for <ledbat@core3.amsl.com>; Sun, 23 Nov 2008 08:12:54 -0800 (PST)
Received: from fruitcake.ICSI.Berkeley.EDU (fruitcake.ICSI.Berkeley.EDU [192.150.186.11]) by core3.amsl.com (Postfix) with ESMTP id DBE6B3A67DB for <ledbat@ietf.org>; Sun, 23 Nov 2008 08:12:54 -0800 (PST)
Received: from [IPv6:::1] (fruitcake [192.150.186.11]) by fruitcake.ICSI.Berkeley.EDU (8.12.11.20060614/8.12.11) with ESMTP id mANGCBTu023579; Sun, 23 Nov 2008 08:12:51 -0800 (PST)
Message-Id: <DC8385BC-9899-48B1-861F-14D94CCB105E@icsi.berkeley.edu>
From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
To: Stanislav Shalunov <shalunov@shlang.com>
In-Reply-To: <80ECA117-243B-49E0-954D-1EF9434E6965@shlang.com>
Mime-Version: 1.0 (Apple Message framework v929.2)
Date: Sun, 23 Nov 2008 08:12:11 -0800
References: <27294E60-8183-47F5-9672-D712E4D85493@icsi.berkeley.edu> <80ECA117-243B-49E0-954D-1EF9434E6965@shlang.com>
X-Mailer: Apple Mail (2.929.2)
Cc: ledbat@ietf.org, Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
Subject: Re: [ledbat] Note well on the BitTorrent problem on the example...
X-BeenThere: ledbat@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Mailing list of the LEDBAT WG <ledbat.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ledbat>, <mailto:ledbat-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/ledbat>
List-Post: <mailto:ledbat@ietf.org>
List-Help: <mailto:ledbat-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ledbat>, <mailto:ledbat-request@ietf.org?subject=subscribe>
Content-Transfer-Encoding: 7bit
Content-Type: text/plain; charset="us-ascii"; Format="flowed"; DelSp="yes"
Sender: ledbat-bounces@ietf.org
Errors-To: ledbat-bounces@ietf.org
I know your example is about a single full-rate TCP flow, not BitTorrent. But your all about the "bad queue" congestion problem, with occurs ALMOST exclusively for people in such situations when doing P2P activity over web-surfing. I'd guess that part of the reason we have gotten away with such grossly asymmetric links is that, outside P2P usage, I'd guess that most users are grossly asymmetric in usage. I know I was, the 3-s uplink buffer on my DSL line only bothered me when I was uploading photos or synchronizing work. On Nov 22, 2008, at 7:41 PM, Stanislav Shalunov wrote: >> it really should be "leech only", > > "Should"? It clearly gets higher download rate for young swarms > with uploading. Even in the most selfish interpretation it > shouldn't be leeching only. > >> as it contributes nothing to the P2P system in practice. > > Incorrect. It contributes close to 128 kb/s, which is not nothing. Its Amdahl's law-related: It really IS close to nothing, and enough that if you care about user performance because you are experiencing head of line blocking issues, that reducing it to 0 is fine. EG. You have 1/2 the peers behind cable-modems, with 1 Mbps uplinks. And you have 1/2 the peers behind slow DSL links, with 128 kbps uplinks. The P2P performance becomes limited by the uplinks in aggregate. And the cable modems contribute 8x the aggregate bandwidth that the DSL links do. In this case, putting ALL the DSL links to 0 upload will have a remarkably low effect on aggregate performance: a degradation of total system upload bandwidth of only 11%. _______________________________________________ ledbat mailing list ledbat@ietf.org https://www.ietf.org/mailman/listinfo/ledbat
- [ledbat] Note well on the BitTorrent problem on t… Nicholas Weaver
- Re: [ledbat] Note well on the BitTorrent problem … Robb Topolski
- Re: [ledbat] Note well on the BitTorrent problem … Nicholas Weaver
- Re: [ledbat] Note well on the BitTorrent problem … Robb Topolski
- Re: [ledbat] Note well on the BitTorrent problem … Laird Popkin
- Re: [ledbat] Note well on the BitTorrent problem … Stanislav Shalunov
- Re: [ledbat] Note well on the BitTorrent problem … Nicholas Weaver
- Re: [ledbat] Note well on the BitTorrent problem … Nicholas Weaver