Re: [p2pi] Information in an ALTO protocol

Nicholas Weaver <nweaver@ICSI.Berkeley.EDU> Mon, 15 September 2008 14:38 UTC

Return-Path: <p2pi-bounces@ietf.org>
X-Original-To: p2pi-archive@ietf.org
Delivered-To: ietfarch-p2pi-archive@core3.amsl.com
Received: from [127.0.0.1] (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 86E343A6B5E; Mon, 15 Sep 2008 07:38:44 -0700 (PDT)
X-Original-To: p2pi@core3.amsl.com
Delivered-To: p2pi@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5744C3A6B40 for <p2pi@core3.amsl.com>; Mon, 15 Sep 2008 07:38:43 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.586
X-Spam-Level:
X-Spam-Status: No, score=-5.586 tagged_above=-999 required=5 tests=[AWL=1.013, 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 WXzXS6sq5FyI for <p2pi@core3.amsl.com>; Mon, 15 Sep 2008 07:38:42 -0700 (PDT)
Received: from fruitcake.ICSI.Berkeley.EDU (fruitcake.ICSI.Berkeley.EDU [192.150.186.11]) by core3.amsl.com (Postfix) with ESMTP id AC03F3A6B5E for <p2pi@ietf.org>; Mon, 15 Sep 2008 07:38:42 -0700 (PDT)
Received: from [IPv6:::1] (fruitcake [192.150.186.11]) by fruitcake.ICSI.Berkeley.EDU (8.12.11.20060614/8.12.11) with ESMTP id m8FEbflv027499; Mon, 15 Sep 2008 07:38:42 -0700 (PDT)
Message-Id: <C0CD1EF3-661C-4861-8BEA-9E6B72C61ABD@icsi.berkeley.edu>
From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
To: Laird Popkin <laird@pando.com>
In-Reply-To: <1666127515.261891221488521592.JavaMail.root@dkny.pando.com>
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Mon, 15 Sep 2008 07:38:41 -0700
References: <1666127515.261891221488521592.JavaMail.root@dkny.pando.com>
X-Mailer: Apple Mail (2.928.1)
Cc: p2pi@ietf.org, Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
Subject: Re: [p2pi] Information in an ALTO protocol
X-BeenThere: p2pi@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: P2P Infrastructure Discussion <p2pi.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/pipermail/p2pi>
List-Post: <mailto:p2pi@ietf.org>
List-Help: <mailto:p2pi-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/p2pi>, <mailto:p2pi-request@ietf.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org

On Sep 15, 2008, at 7:22 AM, Laird Popkin wrote:

> If a p2p application knows roughly what bandwidth the user is  
> provisioned with, it can set reasonable defaults.
>
> For example, Azureus' configuration wizard asks users what kind of  
> uplink speed they have (e.g. dial, 128K, 256K, ..., 1M) and uses  
> different application level values (e.g. max upload speed, number of  
> active transfers, number of active peer connections) appropriate for  
> that kind of network connection. If they could automatically  
> configure themselves rather than asking the user a rather  
> intimidating (to a non-technical consumer) question, that would be  
> better for the users and the network.

If you control a well-connected server, you can probably do this  
pretty easily (at least into the right ballpark) with just a few sets  
of back-to-back UDP packets to estimate uncongested-link bandwidth: at  
least to get

If you do this on startup and IP address change, use 8, 1000B packets  
(4 pairs), and have 10M clients a day doing a test, this would  
require, roughly, 80 GB of upload bandwidth a day.

Given the cost of EC2 as a host for such a test server, this would  
cost a company <$20/day in bandwidth to support 10M clients a day.

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