Re: [p2pi] Information in an ALTO protocol
Stanislav Shalunov <shalunov@shlang.com> Tue, 16 September 2008 01:02 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 86FEA3A6957; Mon, 15 Sep 2008 18:02:31 -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 1D5563A6957 for <p2pi@core3.amsl.com>; Mon, 15 Sep 2008 18:02:31 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.028
X-Spam-Level:
X-Spam-Status: No, score=0.028 tagged_above=-999 required=5 tests=[AWL=1.074, BAYES_00=-2.599, HTML_IMAGE_ONLY_24=1.552, HTML_MESSAGE=0.001]
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 P4nQB+tEiP6f for <p2pi@core3.amsl.com>; Mon, 15 Sep 2008 18:02:30 -0700 (PDT)
Received: from rv-out-0506.google.com (rv-out-0506.google.com [209.85.198.236]) by core3.amsl.com (Postfix) with ESMTP id 2411C3A67A1 for <p2pi@ietf.org>; Mon, 15 Sep 2008 18:02:29 -0700 (PDT)
Received: by rv-out-0506.google.com with SMTP id b25so2220669rvf.49 for <p2pi@ietf.org>; Mon, 15 Sep 2008 18:02:41 -0700 (PDT)
Received: by 10.141.146.4 with SMTP id y4mr5221323rvn.272.1221526961056; Mon, 15 Sep 2008 18:02:41 -0700 (PDT)
Received: from ?10.0.1.234? ( [208.72.192.23]) by mx.google.com with ESMTPS id k2sm23910004rvb.1.2008.09.15.18.02.39 (version=TLSv1/SSLv3 cipher=RC4-MD5); Mon, 15 Sep 2008 18:02:40 -0700 (PDT)
Message-Id: <3DABE53F-A150-4720-8139-D05BD57AE613@shlang.com>
From: Stanislav Shalunov <shalunov@shlang.com>
To: Ye WANG <wangye.thu@gmail.com>
In-Reply-To: <2574b1d30809150709n38627b43va5a4e04fa5ec85df@mail.gmail.com>
Mime-Version: 1.0 (Apple Message framework v926)
Date: Mon, 15 Sep 2008 18:02:38 -0700
References: <48cac5ba.14b48c0a.2f5d.ffffc26f@mx.google.com> <2574b1d30809150709n38627b43va5a4e04fa5ec85df@mail.gmail.com>
X-Mailer: Apple Mail (2.926)
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: multipart/mixed; boundary="===============1800592462=="
Sender: p2pi-bounces@ietf.org
Errors-To: p2pi-bounces@ietf.org
On Sep 15, 2008, at 7:09 AM, Ye WANG wrote: > We have seen many studies on video streaming applications that > prefer higher-uplink-bandwidth peers. I certainly agree with you > that the system may somehow get 'blocked' if all clients naively > select the highest-uplink peer to be parents. Better yet, if this is taken literally, the system turns client/ server: the peers with absolute highest uplinks form the server bank and nobody else uploads anything. This, of course, dramatically reduces swarm efficiency and thus download rates. If done as a preference, the effect is not as extreme, but still a move in the same counterproductive direction. > Analysis based on a fluid model of P2P file sharing system indicates > that bandwidth matching can help improve average file download rate. I'd like to understand this better. I understand the effect with more linear response -- bigger uplink now means proportionally higher uplinks of your peers, which means higher download rate, linearly. I don't yet see why capacity matching will improve average rate. Anyway -- the sublinear response is consciously designed and desirable -- with it, high-capacity peers still have an incentive to contribute, while a majority of peers see improved outcomes. Think of a log(rate) utility function -- 50% better outcomes for 10 typical peers are worth 30% worse outcome for 1 unusually well-provisioned peer. Making the response more linear will improve the outcomes of a few very well-off peers at the expense of a large number of typical ones. I do not yet see why it is desirable. -- Stanislav Shalunov
_______________________________________________ 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