Re: [p2pi] Information in an ALTO protocol
Laird Popkin <laird@pando.com> Mon, 15 September 2008 14:54 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 E55653A6AD5; Mon, 15 Sep 2008 07:54:58 -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 F27F43A68C1 for <p2pi@core3.amsl.com>; Mon, 15 Sep 2008 07:54:57 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -10.091
X-Spam-Level:
X-Spam-Status: No, score=-10.091 tagged_above=-999 required=5 tests=[AWL=0.174, BAYES_00=-2.599, HABEAS_ACCREDITED_COI=-8, IP_NOT_FRIENDLY=0.334]
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 cwFyJIbOW3HC for <p2pi@core3.amsl.com>; Mon, 15 Sep 2008 07:54:53 -0700 (PDT)
Received: from dkny.pando.com (dkny.pando.com [67.99.55.163]) by core3.amsl.com (Postfix) with ESMTP id C76D43A6AFD for <p2pi@ietf.org>; Mon, 15 Sep 2008 07:54:52 -0700 (PDT)
Received: from localhost (localhost.localdomain [127.0.0.1]) by dkny.pando.com (Postfix) with ESMTP id 3DA81E10CD0; Mon, 15 Sep 2008 10:54:59 -0400 (EDT)
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 0e6mJquYiw1d; Mon, 15 Sep 2008 10:54:58 -0400 (EDT)
Received: from dkny.pando.com (dkny.pando.com [10.10.60.11]) by dkny.pando.com (Postfix) with ESMTP id 9EDB4E10A2D; Mon, 15 Sep 2008 10:54:58 -0400 (EDT)
Date: Mon, 15 Sep 2008 10:54:58 -0400
From: Laird Popkin <laird@pando.com>
To: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
Message-ID: <656411879.262961221490498621.JavaMail.root@dkny.pando.com>
In-Reply-To: <C0CD1EF3-661C-4861-8BEA-9E6B72C61ABD@icsi.berkeley.edu>
MIME-Version: 1.0
X-Originating-IP: [10.10.20.61]
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
The cost of bandwidth testing isn't terrible, but the accuracy of measurements taken on 1K transfers is very low - you're really measuring latency and buffering, not sustained data transfer rate. Of course, there might be some relationship between them, but (at least in our measurements) it took much larger data transfers to get even remotely stable results. In addition, measuring actual throughput at a point in time can be affected by other traffic on the PC (e.g. PC's do many things when they're starting up), other nearby PC's (e.g. someone else in your neighborhood is busy right now), transient interference on the internet, etc. So while it's not unreasonable to do such testing, and we certainly do so, an ISP provided provisioned capacity would be much more accurate (when it's available). - Laird Popkin, CTO, Pando Networks mobile: 646/465-0570 ----- Original Message ----- From: "Nicholas Weaver" <nweaver@ICSI.Berkeley.EDU> To: "Laird Popkin" <laird@pando.com> Cc: "Nicholas Weaver" <nweaver@ICSI.Berkeley.EDU>, "Ye WANG" <wangye.thu@gmail.com>, p2pi@ietf.org Sent: Monday, September 15, 2008 10:38:41 AM (GMT-0500) America/New_York Subject: Re: [p2pi] Information in an ALTO protocol 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
- [p2pi] Information in an ALTO protocol Enrico Marocco
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Vinay Aggarwal
- Re: [p2pi] Information in an ALTO protocol Lars Eggert
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol chsoft
- Re: [p2pi] Information in an ALTO protocol Vinay Aggarwal
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Nicholas Weaver
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol Sebastian Kiesel
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Fabio Hecht
- Re: [p2pi] Information in an ALTO protocol Song Haibin
- Re: [p2pi] Information in an ALTO protocol Vijay K. Gurbani
- Re: [p2pi] Information in an ALTO protocol David R Oran
- Re: [p2pi] Information in an ALTO protocol Spencer Dawkins
- Re: [p2pi] Information in an ALTO protocol Lisa Dusseault
- Re: [p2pi] Information in an ALTO protocol David R Oran
- Re: [p2pi] Information in an ALTO protocol Lisa Dusseault
- Re: [p2pi] Information in an ALTO protocol David R Oran
- Re: [p2pi] Information in an ALTO protocol Reinaldo Penno
- Re: [p2pi] Information in an ALTO protocol Lisa Dusseault
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Reinaldo Penno
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Salman Abdul Baset
- Re: [p2pi] Information in an ALTO protocol Griffiths, Chris
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol stefano previdi
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol stefano previdi
- Re: [p2pi] Information in an ALTO protocol Woundy, Richard
- Re: [p2pi] Information in an ALTO protocol stefano previdi
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Ye WANG
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Nicholas Weaver
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Nicholas Weaver
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Philip Levis
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Stanislav Shalunov
- Re: [p2pi] Information in an ALTO protocol Ye WANG
- Re: [p2pi] Information in an ALTO protocol The 8472
- Re: [p2pi] Information in an ALTO protocol Laird Popkin
- Re: [p2pi] Information in an ALTO protocol Salman Abdul Baset