From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: X-Spam-Status: No, score=-4.0 required=3.0 tests=ALL_TRUSTED,BAYES_00 shortcircuit=no autolearn=ham autolearn_force=no version=3.4.1 Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 191BA1F453; Fri, 2 Nov 2018 20:36:59 +0000 (UTC) Date: Fri, 2 Nov 2018 20:36:58 +0000 From: Eric Wong To: Konstantin Ryabitsev , Yaron Scheffer Cc: meta@public-inbox.org Subject: Re: Corrupted lkml repo? Message-ID: <20181102203658.otux6kwxsr3wh37y@dcvr> References: <20181030153806.GB9025@pure.paranoia.local> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline In-Reply-To: <20181030153806.GB9025@pure.paranoia.local> List-Id: Konstantin Ryabitsev wrote: > On Tue, Oct 30, 2018 at 03:55:23AM +0000, Yaron Scheffer wrote: > > > > Several attempts spread over several days to git clone > > > > https://lore.kernel.org/lkml/0 > > > > The process fails with the error "server hung up > > unexpectedly", at right about the 100% mark. > > > > Is anyone else seeing this? > > You're hitting a timeout on the AWS side of things that we can't extend. > Please clone from our mirror instead: Konstantin: Is that time-to-first-byte, overall transfer time or something to do with POST requests being treated differently? Yaron: does disabling smart HTTP to rely on only GET transfers improve things? Smart HTTP is great for bandwidth reduction but uses more CPU/memory on the server side, and perhaps recommending clients do that for big repos is a good thing anyways for the initial clone. GIT_SMART_HTTP=0 git clone --mirror ...