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 5C7A321F21F for ; Tue, 21 Apr 2015 07:28:48 -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 t3LESjwI020265; Tue, 21 Apr 2015 07:28:46 -0700 Date: Tue, 21 Apr 2015 07:28:45 -0700 (PDT) From: David Lang X-X-Sender: dlang@asgard.lang.hm To: jb In-Reply-To: Message-ID: References: <75C1DDFF-FBD2-4825-A167-92DFCF6A7713@gmail.com> <8AD4493E-EA21-496D-923D-B4257B078A1C@gmx.de> <8E4F61CA-4274-4414-B4C0-F582167D66D6@gmx.de> <2C987A4B-7459-43C1-A49C-72F600776B00@gmail.com> <14cd9e74e48.27f7.e972a4f4d859b00521b2b659602cb2f9@superduper.net> User-Agent: Alpine 2.02 (DEB 1266 2009-07-14) MIME-Version: 1.0 Content-Type: MULTIPART/Mixed; BOUNDARY="680960-939992269-1429626018=:26044" Content-ID: Cc: bloat Subject: Re: [Bloat] DSLReports Speed Test has latency measurement built-in 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: Tue, 21 Apr 2015 14:28:49 -0000 This message is in MIME format. The first part should be readable text, while the remaining parts are likely unreadable without MIME-aware tools. --680960-939992269-1429626018=:26044 Content-Type: TEXT/PLAIN; FORMAT=flowed; CHARSET=US-ASCII Content-ID: On Tue, 21 Apr 2015, David Lang wrote: > On Tue, 21 Apr 2015, David Lang wrote: > >>> I suspect you guys are going to say the server should be left with a large >>> max receive window.. and let people complain to find out what their issue >>> is. >> >> what is your customer base? how important is it to provide faster service >> to teh fiber users? Are they transferring ISO images so the difference is >> significant to them? or are they downloading web pages where it's the >> difference between a half second and a quarter second? remember that you >> are seeing this on the upload side. >> >> in the long run, fixing the problem at the client side is the best thing to >> do, but in the meantime, you sometimes have to work around broken customer >> stuff. > > for the speedtest servers, it should be set large, the purpose is to test the > quality of the customer stuff, so you don't want to do anything on your end > that papers over the problem, only to have the customer think things are good > and experience problems when connecting to another server that doesn't > implement work-arounds. Just after hitting send it occured to me that it may be the right thing to have the server that's being hit by the test play with these settings. If the user works well at lower settings, but has problems at higher settings, the point where they start having problems may be useful to know. David Lang --680960-939992269-1429626018=:26044 Content-Type: TEXT/PLAIN; CHARSET=us-ascii Content-ID: Content-Description: Content-Disposition: INLINE _______________________________________________ Bloat mailing list Bloat@lists.bufferbloat.net https://lists.bufferbloat.net/listinfo/bloat --680960-939992269-1429626018=:26044--