From: Eric Wong <e@80x24.org>
To: Yaron Scheffer <yscheffer@protonmail.com>
Cc: Konstantin Ryabitsev <konstantin@linuxfoundation.org>,
meta@public-inbox.org
Subject: Re: Corrupted lkml repo?
Date: Sun, 4 Nov 2018 03:50:17 +0000 [thread overview]
Message-ID: <20181104035017.rmlr3sf7wybwuvo6@untitled> (raw)
In-Reply-To: <cwgWka22oKijsGrzoKQvV5SQCqS_Cg0KQYijk6X7edfDzTmvX4i0irDTKiTAMnGJwTKErxqD5PzZQLE6pKw5-Z3oizcroCW-ALkbuWX01Gg=@protonmail.com>
Yaron Scheffer <yscheffer@protonmail.com> wrote:
> Eric Wong wrote:
>
> > 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 ...
>
> Maybe, but If "git clone" stresses the server to the point of breakage
> as you say, something should be done on the server side. I've been
> using the kernel.org repo as Konstantin suggested.
Based on Konstantin's message; it didn't seem like the server
itself was stressed, just something on Amazon's side.
> Perhaps lower the recommended maximum shard size? I didn't hit
> this issue with the most recent shard, which is about 50% smaller.
That's another option; but migrating/converting existing repos
to it would be a flag day and break existing mirrors.
~1G seemed like a reasonable starting point
next prev parent reply other threads:[~2018-11-04 3:50 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 3:55 Corrupted lkml repo? Yaron Scheffer
2018-10-30 15:38 ` Konstantin Ryabitsev
2018-11-02 20:36 ` Eric Wong
2018-11-03 8:34 ` Yaron Scheffer
2018-11-04 3:50 ` Eric Wong [this message]
2018-11-05 13:20 ` Konstantin Ryabitsev
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://public-inbox.org/README
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181104035017.rmlr3sf7wybwuvo6@untitled \
--to=e@80x24.org \
--cc=konstantin@linuxfoundation.org \
--cc=meta@public-inbox.org \
--cc=yscheffer@protonmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://80x24.org/public-inbox.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).