Re: [ledbat] Note well on the BitTorrent problem on the example...

Laird Popkin <laird@pando.com> Thu, 20 November 2008 23:55 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 C7E8E3A6A48; Thu, 20 Nov 2008 15:55:39 -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 68FC63A6984 for <ledbat@core3.amsl.com>; Thu, 20 Nov 2008 15:55:38 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -9.664
X-Spam-Level:
X-Spam-Status: No, score=-9.664 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, HABEAS_ACCREDITED_COI=-8, HTML_MESSAGE=0.001, IP_NOT_FRIENDLY=0.334, J_CHICKENPOX_24=0.6]
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 AeAPcOUf6YvZ for <ledbat@core3.amsl.com>; Thu, 20 Nov 2008 15:55:37 -0800 (PST)
Received: from dkny.pando.com (dkny.pando.com [67.99.55.163]) by core3.amsl.com (Postfix) with ESMTP id D64FD3A6A35 for <ledbat@ietf.org>; Thu, 20 Nov 2008 15:55:36 -0800 (PST)
Received: from localhost (localhost.localdomain [127.0.0.1]) by dkny.pando.com (Postfix) with ESMTP id E0EF5E10B24; Thu, 20 Nov 2008 18:55:32 -0500 (EST)
X-Virus-Scanned: amavisd-new at
Received: from dkny.pando.com ([127.0.0.1]) by localhost (dkny.pando.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 1IarckIPxwu1; Thu, 20 Nov 2008 18:55:19 -0500 (EST)
Received: from dkny.pando.com (dkny.pando.com [10.10.60.11]) by dkny.pando.com (Postfix) with ESMTP id 9E9B9E10B17; Thu, 20 Nov 2008 18:55:19 -0500 (EST)
Date: Thu, 20 Nov 2008 18:55:19 -0500
From: Laird Popkin <laird@pando.com>
To: Robb Topolski <robb@funchords.com>
Message-ID: <570928620.115911227225319609.JavaMail.root@dkny.pando.com>
In-Reply-To: <1460863631.115891227225138256.JavaMail.root@dkny.pando.com>
MIME-Version: 1.0
X-Originating-IP: [10.10.20.77]
Cc: ledbat@ietf.org
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-Type: multipart/mixed; boundary="===============0660984679=="
Sender: ledbat-bounces@ietf.org
Errors-To: ledbat-bounces@ietf.org

This is a good point. 

Keep in mind that tit-for-tat (i.e. sending as much as you receive with each peer) is only enforced between downloaders - anyone who has completed downloading contributes freely and does not get anything in return. Even between downloaders, tit-for-tat is not enforced absolutely, but only very approximately. 

Also keep in mind that not all p2p networks use tit-for-tat. So while it's certainly useful to think about the BitTorrent case, there are many other kinds of p2p network (e.g. live streaming) that care more about other attributes (e.g. latency) rather than fairness between peers. 

- Laird Popkin, CTO, Pando Networks 
mobile: 646/465-0570 

----- Original Message ----- 
From: "Robb Topolski" <robb@funchords.com> 
To: "Nicholas Weaver" <nweaver@icsi.berkeley.edu> 
Cc: ledbat@ietf.org 
Sent: Thursday, November 20, 2008 6:06:29 PM (GMT-0500) America/New_York 
Subject: Re: [ledbat] Note well on the BitTorrent problem on the example... 

Replies inline... 


On Thu, Nov 20, 2008 at 12:48 PM, Nicholas Weaver < nweaver@icsi.berkeley.edu > wrote: 




In the aggregate, a bulk-data P2P system must upload as much as it downloads, and your performance becomes limited by uplink bandwidth. 

We can start here, although I know it's not the crux of your point. 

"In the aggregate," true, but "your performance" is not in that context -- its yours alone. 

I think the value of 1:1 up:down participation on an individual basis is overrated if not unhealthy (if not unattainable). There will always be some last downloader in a swarm -- who is he going to upload to? How many swarms that should have died stay alive (and perform poorly) in a futile effort for someone to reach their 1:1 goal? 

Such goals forget that some people value getting their own interests out there, and are motivated to spend their energy (and bandwidth) in doing that (quickly/broadly/efficiently etc) and that activity is further skewed based on their preferences (linux, anime, porn, first-run movies, software, old music, amateur documentaries). 




When you have a significant group of hosts with a near-zero uplink, these hosts contribute very little to the overall performance of the system. 



EG, if 1/2 of the systems are cable modems with 1 Mbps uplink, and 1/2 are behind 128 kb uplink, the aggregate system bandwidth is 8-1: for every single bit of uplink from the DSL lines, you get 8x the uplink from the cable modem lines. 

At such a point, you might as well, from an aggregate system viewpoint, reduce the upload of the DSL hosts to 0: they are contributing so little, but experiencing a huge degredation of performance that MUST occur because of the minimum buffer size of a few packets. 
. 


If two dial-up users are reciprocatively sharing chunks of files, that's two slots from the universe of other peer's uploading slots that they won't occupy. It's an efficient pairing. It would be inefficient for one of these dialup users to occupy the upload slot of a cablemodem user for any extended time. (Some clients will open an additional slot if this happens, but that enhanced behavior is optional, and an uploader still won't spend significant time servicing a slow downloader). 

Could those 128 Kb uploaders service ISDN or Satellite users? Or maybe pair up with a dial-up user (slow but better than 1 Mbps transferring to dial-up)? 






You can NEVER size a buffer for a DSL modem for normal TCP such that you will get good interactive behavior while a full rate upload occurs. 


This is the part that got my attention. These aren't like the old phone modems with flow control, so that's why they have this problem? (This isn't really a P2P-related problem, is it?) 



In contrast, you can use an effectivev 100-150ms buffer on the cable modems, so they can get full rate TCP but at the same time, not step on their interactive traffic (subequent message coming on that). 


I'll watch for it. I wasn't aware that one had less of a problem than the other. 

Thanks Nick! 

Robb 


-- 
Robb Topolski ( robb@funchords.com ) 
Hillsboro, Oregon USA 
http://www.funchords.com/ 

_______________________________________________ ledbat mailing list ledbat@ietf.org https://www.ietf.org/mailman/listinfo/ledbat 
_______________________________________________
ledbat mailing list
ledbat@ietf.org
https://www.ietf.org/mailman/listinfo/ledbat