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 D5F6021FD3A for ; Fri, 7 Aug 2015 07:35:10 -0700 (PDT) X-Virus-Scanned: amavisd-new at mail2.tohojo.dk DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=toke.dk; s=201310; t=1438958102; bh=cGmggUGDzbP8LRrLOCKlMRcoBuabHzGCeRZ7lt3YhWA=; h=From:To:Cc:Subject:References:Date:In-Reply-To; b=J2HrzZFwsjUTHezEq2WxjqrfmCRTYPE7V6rjCycdnrbQ5uQ9nwV6/B0OCjA7x5363 AWuGZkwyRQMTt4N4bSWcDN/jz7PggCGttgqTxyT7TKKeANa3T+XuJCAIOTxfmoYztK vXlGiMWoaBZbb3xhr3Wt5CUe5J8wU2ttj55bEvIk= Sender: toke@toke.dk Received: by alrua-x1.borgediget.toke.dk (Postfix, from userid 1000) id 4382442B05; Fri, 7 Aug 2015 16:35:00 +0200 (CEST) From: =?utf-8?Q?Toke_H=C3=B8iland-J=C3=B8rgensen?= To: Mikael Abrahamsson References: <4EDA85BE-CD86-4DA9-8ED5-78500E858F79@baylink.com> <20150807142337.GA22258@sesse.net> Date: Fri, 07 Aug 2015 16:35:00 +0200 In-Reply-To: (Mikael Abrahamsson's message of "Fri, 7 Aug 2015 16:28:49 +0200 (CEST)") X-Clacks-Overhead: GNU Terry Pratchett Message-ID: <87r3nfqi97.fsf@toke.dk> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Cc: bloat@lists.bufferbloat.net Subject: Re: [Bloat] Fwd: Did *bufferbloat* cause the 2010 flashcrash? 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: Fri, 07 Aug 2015 14:35:39 -0000 Mikael Abrahamsson writes: > On Fri, 7 Aug 2015, Steinar H. Gunderson wrote: > >> [1] For the purposes of the question, the =E2=80=9CBitTorrent problem=E2= =80=9D is when you and >> I are on the same network, and your 200+ BitTorrent upload sessions make= s it >> impossible for me to upload my single cat video to YouTube. > > Isn't this dependent on the upload speed? I would imagine that if it's 5-= 10 > megabit/s, then using Codel or similar technique that doesn't allow the b= uffer > to grow to hundreds of milliseconds, would improve things a lot? > > For a 500 kilobit/s link, I'm not sure even that would work...? There are two separate issues:=20 -Toke