Re: [p2pi] Information in an ALTO protocol

Nicholas Weaver <nweaver@ICSI.Berkeley.EDU> Mon, 15 September 2008 15:07 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 2EC2528C160; Mon, 15 Sep 2008 08:07:14 -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 3C37A28C160 for <p2pi@core3.amsl.com>; Mon, 15 Sep 2008 08:07:12 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -5.639
X-Spam-Level:
X-Spam-Status: No, score=-5.639 tagged_above=-999 required=5 tests=[AWL=0.960, 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 n8z2X9mZ4gWp for <p2pi@core3.amsl.com>; Mon, 15 Sep 2008 08:07:11 -0700 (PDT)
Received: from fruitcake.ICSI.Berkeley.EDU (fruitcake.ICSI.Berkeley.EDU [192.150.186.11]) by core3.amsl.com (Postfix) with ESMTP id 77BFC28C126 for <p2pi@ietf.org>; Mon, 15 Sep 2008 08:07:11 -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 m8FF6esO000565; Mon, 15 Sep 2008 08:07:20 -0700 (PDT)
Message-Id: <CD44B86C-C2EA-416E-91C8-17875AD19C21@ICSI.Berkeley.EDU>
From: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
To: Laird Popkin <laird@pando.com>
In-Reply-To: <656411879.262961221490498621.JavaMail.root@dkny.pando.com>
Mime-Version: 1.0 (Apple Message framework v928.1)
Date: Mon, 15 Sep 2008 08:06:40 -0700
References: <656411879.262961221490498621.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:54 AM, Laird Popkin wrote:

> 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).

The point of the 1K back-to-back packets is NOT that you are testing  
the transfer time for the 1K packets, but that interarrival time of  
the packets can be used as an uncongested-link bandwidth estimate, as  
long as the queue at the point of congestion uses FIFO delivery of  
packets.

Since the question you are asking the user is "whats the UNCONGESTED"  
behavior as a starting point (to set an initial threshold/ceiling  
somewhere below this point), the behavior of back-to-back packets  
should get you in the right ballpark without having to ask the user.


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