From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail1.bemta32.messagelabs.com (mail1.bemta32.messagelabs.com [195.245.230.1]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by lists.bufferbloat.net (Postfix) with ESMTPS id 67C403B2A4 for ; Thu, 1 Sep 2022 05:12:36 -0400 (EDT) X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrFIsWRWlGSWpSXmKPExsXSsnPhFt2mcoF kg3VnJS3a+m6xWiy5aGuxdvEWVgdmjw8f4zx+PDvB7rH94hmmAOYo1sy8pPyKBNaMX1deshTs 5ahonruCqYHxLVsXIxeHkMAORol/2/ewQzjLGCVmPZ4LlTnNKLFwwkrmLkZOIKde4sCKRSwgN ouAisTU5VPZQWw2AQOJiT//sYHYIgJyEvOfXmIEaWYW2M8o8ffLbLCEsICexM325WDNvAIWEh POfmWBGConcbHlC9TqN8wSO153s3YxcgAVCUr83SEMUsMsoCVx499LJpAws4C0xPJ/HCBhTgF LiQdbNjFNYBSYhdAwC0nDLISGBYzMqxgtk4oy0zNKchMzc3QNDQx0DQ1NdY11Lcz0Eqt0E/VS S3XLU4tLdA31EsuL9VKLi/WKK3OTc1L08lJLNjECgzylmDlsB+Of3p96hxglOZiURHn7dQSSh fiS8lMqMxKLM+KLSnNSiw8xynBwKEnwPiwAygkWpaanVqRl5gAjDiYtwcGjJML7oxAozVtckJ hbnJkOkTrFqCglzjs5CyghAJLIKM2Da4NF+SVGWSlhXkYGBgYhnoLUotzMElT5V4ziHIxKwrw rS4Gm8GTmlcBNfwW0mAlo8fSZ/CCLSxIRUlINTIznGe5s9PiTaOj4d5YYm1Q9w1aRqYtvrTO+ tj5Vd7Kz/OVNjNslLfefybvz8DRLTNj/XWdDHi9jOGriyfQw/oPZbzUlPaFkw0+zVU+pz5je+ fe4fs4vw61pzLsF+fYfmjVD800vpyL3jsI/HGrby/T5Ijn9Q2Yo+iQ2rVKLVtvvGS34iC3cg6 FAjvdultGMd58n3UqdWJMcXH/oYe/HRfMY3XR/zPV8HbqArTZL8fBPHr/q7NMKtz/1fr/Wtmn TlmbPi5o/NncunrkwY/Ux1bKeI1JPrE5sdz02a3lox63Dyos3Lmk/brpiTblbksT+dV8P8l/d dHt6160qW5Ht5W9nLvZeKLFdt+jzjjnij6KUWIozEg21mIuKEwEjenMZbQMAAA== X-Env-Sender: brandon@rd.bbc.co.uk X-Msg-Ref: server-16.tower-561.messagelabs.com!1662023554!5457!1 X-Originating-IP: [132.185.161.180] X-SYMC-ESS-Client-Auth: outbound-route-from=pass X-StarScan-Received: X-StarScan-Version: 9.87.3; banners=-,-,- X-VirusChecked: Checked Received: (qmail 15022 invoked from network); 1 Sep 2022 09:12:34 -0000 Received: from mailout1.telhc.bbc.co.uk (HELO mailout1.telhc.bbc.co.uk) (132.185.161.180) by server-16.tower-561.messagelabs.com with ECDHE-RSA-AES256-GCM-SHA384 encrypted SMTP; 1 Sep 2022 09:12:34 -0000 Received: from gateb.lh.bbc.co.uk (gateb.kw.bbc.co.uk [132.185.132.11]) by mailout1.telhc.bbc.co.uk (8.15.2/8.15.2) with ESMTP id 2819CY9O021285; Thu, 1 Sep 2022 10:12:34 +0100 (BST) Received: from mailhub1.rd.bbc.co.uk ([172.29.120.129]) by gateb.lh.bbc.co.uk (8.15.1+Sun/8.13.6) with ESMTP id 2819CXVV020026; Thu, 1 Sep 2022 10:12:33 +0100 (BST) Received: from sunf10.rd.bbc.co.uk ([132.185.128.110]:45207) by mailhub1.rd.bbc.co.uk with esmtp (Exim 4.92) (envelope-from ) id 1oTgFV-0003QE-Pl; Thu, 01 Sep 2022 10:12:33 +0100 Received: (from brandon@localhost) by sunf10.rd.bbc.co.uk (8.9.3+Sun/8.9.3) id KAA00210; Thu, 1 Sep 2022 10:12:33 +0100 (BST) Date: Thu, 1 Sep 2022 10:12:33 +0100 From: Brandon Butterworth To: David Lang Cc: Brandon Butterworth , Sebastian Moeller , Ulrich Speidel via Starlink , brandon@rd.bbc.co.uk Message-ID: <20220901091233.GA29719@sunf10.rd.bbc.co.uk> Reply-To: brandon@rd.bbc.co.uk References: <1661878433.14064713@apps.rackspace.com> <6p5n9262-3745-pq31-5636-1rnon987o255@ynat.uz> <20220830220710.GA2653@sunf10.rd.bbc.co.uk> <15982a40-2b34-7ed1-bfa3-bced03fc3839@auckland.ac.nz> <9CE05D69-FC37-4C97-9D8D-D46B2DF6DE16@gmx.de> <2321be3b-957f-2d1f-c335-119c8e76efe5@auckland.ac.nz> <23E930C0-23A5-4ACC-BAB7-D057CD2D8572@gmx.de> <20220831092541.GA9165@sunf10.rd.bbc.co.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Subject: Re: [Starlink] Starlink "beam spread" X-BeenThere: starlink@lists.bufferbloat.net X-Mailman-Version: 2.1.20 Precedence: list List-Id: "Starlink has bufferbloat. Bad." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Sep 2022 09:12:36 -0000 On Wed Aug 31, 2022 at 02:34:04AM -0700, David Lang wrote: > On Wed, 31 Aug 2022, Brandon Butterworth via Starlink wrote: > > >With Starlink capacity being multiplexed per Dishy and uplink > >and downlink capacity equal on each satellite there doesn't appear > >to be any sharing gain to be had there warranting a CDN in space. > > don't forget that there are also the laser links, they could link you to a > shared space CDN, and they also 'complicate' the uplink/downlink > calculations for any one satellite. That was the subject of the following paragraphs. I agree that is likely the key enabler for a space CDN. Some mentioned SSD density is too high for space. We're used to some hard errors in flash, is the space error rate too high to cope with, even with increased sparing? Or is it the soft error rate that is too high? At least for a CDN the soft rate is less of an issue as it is invalidating cache entries all the time, this is just a new reason to that requires detecting, and perhaps a less than whole file invaliation for more efficient replacement. brandon