From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from bifrost.lang.hm (mail.lang.hm [64.81.33.126]) (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 1B65721F332 for ; Mon, 20 Apr 2015 08:45:40 -0700 (PDT) Received: from asgard.lang.hm (asgard.lang.hm [10.0.0.100]) by bifrost.lang.hm (8.13.4/8.13.4/Debian-3) with ESMTP id t3KFjcIk013943; Mon, 20 Apr 2015 08:45:38 -0700 Date: Mon, 20 Apr 2015 08:45:38 -0700 (PDT) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: sahil grover In-Reply-To: Message-ID: References: User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: TEXT/Plain; format=flowed; charset=US-ASCII Cc: bloat@lists.bufferbloat.net Subject: Re: [Bloat] Realtime Response Under Load (RRUL) Test 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, 20 Apr 2015 15:46:09 -0000 On Mon, 20 Apr 2015, sahil grover wrote: > David Sir, > > Thanks for answering. > > can you please tell me how to interpret its output? > > By "netperf-wrapper rrul netperf.bufferbloat.net" ( i chose netserver > that is running on netperf.bufferbloat.net) > output(result.png) is attached. > > please tell me first what does it say generally? > secondly, anything related with bufferbloat point of view. latency should not increase significantly under load. The fact that it does indicates that you have a problem. The fact that the latency can increase to multi-second values for many people indicates a big problem. take a look at the new test that's available at https://www.dslreports.com/speedtest and then look at the results tab and see how the latency increases during the download and upload tests. If you have a system without excessive buffering, you would not see massive increases in latency. Contact me off-list if you want a deeper discussion of the history of bufferbloat and what's going on to try and solve it. David Lang