Re: [p2pi] Information in an ALTO protocol

Philip Levis <pal@cs.stanford.edu> Mon, 15 September 2008 18:27 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 D0D9D3A6ABA; Mon, 15 Sep 2008 11:27: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 ADD923A6ABA for <p2pi@core3.amsl.com>; Mon, 15 Sep 2008 11:27:13 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.297
X-Spam-Level:
X-Spam-Status: No, score=-6.297 tagged_above=-999 required=5 tests=[AWL=0.302, 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 28WnE5thitwc for <p2pi@core3.amsl.com>; Mon, 15 Sep 2008 11:27:12 -0700 (PDT)
Received: from cs-smtp-2.Stanford.EDU (cs-smtp-2.Stanford.EDU [171.64.64.26]) by core3.amsl.com (Postfix) with ESMTP id E9CCC3A698F for <p2pi@ietf.org>; Mon, 15 Sep 2008 11:27:12 -0700 (PDT)
Received: from dnab4232e1.stanford.edu ([171.66.50.225]) by cs-smtp-2.Stanford.EDU with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.60) (envelope-from <pal@cs.stanford.edu>) id 1KfInD-0006xy-P9; Mon, 15 Sep 2008 11:27:24 -0700
Message-Id: <C8109766-4E40-4C63-B0B6-507B59DAE3BA@cs.stanford.edu>
From: Philip Levis <pal@cs.stanford.edu>
To: Nicholas Weaver <nweaver@ICSI.Berkeley.EDU>
In-Reply-To: <CD44B86C-C2EA-416E-91C8-17875AD19C21@ICSI.Berkeley.EDU>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Mon, 15 Sep 2008 10:18:46 -0700
References: <656411879.262961221490498621.JavaMail.root@dkny.pando.com> <CD44B86C-C2EA-416E-91C8-17875AD19C21@ICSI.Berkeley.EDU>
X-Mailer: Apple Mail (2.926)
X-Scan-Signature: 2d1a4fa5d0150c38835749a59b44c419
Cc: p2pi@ietf.org
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 8:06 AM, Nicholas Weaver wrote:

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

Nick,

I think you're talking about a theoretical "should" and Laird is  
talking about what he's observed in practice.

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