From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail2.tohojo.dk (mail2.tohojo.dk [77.235.48.147]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by huchra.bufferbloat.net (Postfix) with ESMTPS id 8A63A21F22D for ; Mon, 27 Apr 2015 06:01:18 -0700 (PDT) X-Virus-Scanned: amavisd-new at mail2.tohojo.dk Received: by alrua-kau.kau.toke.dk (Postfix, from userid 1000) id D4A9FC40134; Mon, 27 Apr 2015 15:01:09 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=toke.dk; s=201310; t=1430139670; bh=2LLvTDHEBq4/jA73pkj0PTK4IhLz6KKj60BzYE4MQhI=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=jwmVq9vY2LcEszF+mVVqYHmnrXxia6Fcm3jAGBIwKhhAJBQOhfyobAaa2i99nOY5M tMdaXpkgCeFZfEKdT07+4zSyar6fZl7Rf5U+0FG9Po8vG/ooco869P1A4nZ3SrQVs5 X6BCGo689uo/ROemXaPZAnKLvZb/OPYe+sncC2Qo= From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: Paolo Valente References: <3E2406CD-0938-4C1F-B171-247CBB5E4C7D@unimore.it> <87zj5u2aho.fsf@toke.dk> <2B5B39C9-A33D-46ED-84C6-56F237284B21@unimore.it> <87pp6p22ho.fsf@toke.dk> Date: Mon, 27 Apr 2015 15:01:09 +0200 In-Reply-To: (Paolo Valente's message of "Mon, 27 Apr 2015 14:45:08 +0200") X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87lhhd20a2.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain Cc: bloat Subject: Re: [Bloat] bufferbloat effects on throughput X-BeenThere: bloat@lists.bufferbloat.net X-Mailman-Version: 2.1.13 Precedence: list List-Id: General list for discussing Bufferbloat List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 27 Apr 2015 13:01:47 -0000 Paolo Valente writes: > One question: how can one be sure (if it is possible) that the > fluctuation of the throughput of a TCP flow on a given node is caused > by bufferbloat issues in the node, and not by other factors (such as, > e.g., systematic drops in some other nodes along the path followed by > the flow, with the drops possibly even caused by different reasons > than bufferbloat)? You can't, and it might. However, if you measure a performance degradation that goes away when the link is idle, consider that a hint... :) -Toke