From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from cirse-smtp-out.extra.cea.fr (cirse-smtp-out.extra.cea.fr [132.167.192.148]) (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 CA64B3B2A4 for ; Sat, 3 Feb 2024 15:11:03 -0500 (EST) Received: from pisaure.intra.cea.fr (pisaure.intra.cea.fr [132.166.88.21]) by cirse-sys.extra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 413KB2Kh027553 for ; Sat, 3 Feb 2024 21:11:02 +0100 Received: from pisaure.intra.cea.fr (localhost [127.0.0.1]) by localhost (Postfix) with SMTP id 5C40F203357 for ; Sat, 3 Feb 2024 21:11:02 +0100 (CET) Received: from muguet2-smtp-out.intra.cea.fr (muguet2-smtp-out.intra.cea.fr [132.166.192.13]) by pisaure.intra.cea.fr (Postfix) with ESMTP id 52BD520334E for ; Sat, 3 Feb 2024 21:11:02 +0100 (CET) Received: from [10.14.0.28] ([10.14.0.28]) by muguet2-sys.intra.cea.fr (8.14.7/8.14.7/CEAnet-Internet-out-4.0) with ESMTP id 413KB1vV049883 for ; Sat, 3 Feb 2024 21:11:02 +0100 Message-ID: <0eb6e6dc-f9e3-400b-ba7e-695aa5ea5b6a@gmail.com> Date: Sat, 3 Feb 2024 21:11:01 +0100 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Content-Language: fr To: starlink@lists.bufferbloat.net References: From: Alexandre Petrescu In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit X-CEA-Virus: SOPHOS_SAVI_ERROR_OLD_VIRUS_DATA Subject: Re: [Starlink] 42 petabytes/day and ... 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: Sat, 03 Feb 2024 20:11:03 -0000 Le 02/02/2024 à 04:07, Dave Taht via Starlink a écrit : > from here: https://news.ycombinator.com/item?id=39200323 > > There were two things that fell out of reading that article for me. > > "each laser is grossly underused on average, at 0.432% of its maximum capacity." > > + > > "Brashears also said Starlink’s laser system was able to connect two > satellites over 5,400 kilometers (3,355 miles) apart. The link was so > long “it cut down through the atmosphere, all the way down to 30 > kilometers above the surface of the Earth,” he said, before the > connection broke." It looks spectacular. A starlink latency of say 40ms on such a long distance 5400km between sats seems remarkable.  Note that the corresponding on-ground distance between two homes served by these two sats would be smaller, perhaps 3000km(?). It is easy to compare that via-stalink latency to a ping RTT on a ground only link on comparable distance. Alex > > So there IS a way to achieve previously unheard of lower latencies (at > a cost in bitrate) across starlink across their network. Two hops to > go 10,000km. > > I loved mark handley's original animation of how the ISL's were > supposed to work, but given the orbits here, I kind of wish it was > easy to plug the assumptions in and figure out what the NY -> tokoyo > run would take in terms of hops and estimated switching overhead, > given this distance record. > > How much data and what kind of data would benefit from that latency > reduction is a matter of speculation. "Buy! Sell!" between tokoyo and > london arbitrage was one of my first speculations many years ago. >