From: Eric Wong <e@80x24.org>
To: git@vger.kernel.org
Subject: Re: Strategy to deal with slow cloners
Date: Wed, 21 Apr 2021 20:08:16 +0000 [thread overview]
Message-ID: <20210421200816.GA13772@dcvr> (raw)
In-Reply-To: <20210419180803.GA10171@dcvr>
Eric Wong <e@80x24.org> wrote:
> Konstantin Ryabitsev <konstantin@linuxfoundation.org> wrote:
> > Hello:
> >
> > I try to keep repositories routinely repacked and optimized for clones, in
> > hopes that most operations needing lots of objects would be sending packs
> > straight from disk. However, every now and again a client from a slow
> > connection requests a large clone and then takes half a day downloading it,
> > resulting in gigabytes of RAM being occupied by a temporary pack.
>
> Yeah, I'm familiar with the problem.
Also, AFAIK nginx has "proxy_buffering on" by default. However,
I seem to recall that prevents clients from seeing a single byte
until the pack is completely generated. It's been many years
since I've used nginx myself, so my knowledge about it could be
out-of-date.
next prev parent reply other threads:[~2021-04-21 20:08 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-19 12:46 Strategy to deal with slow cloners Konstantin Ryabitsev
2021-04-19 18:08 ` Eric Wong
2021-04-21 20:08 ` Eric Wong [this message]
2021-04-20 14:52 ` Thomas Braun
2021-04-22 9:16 ` Ævar Arnfjörð Bjarmason
2021-04-23 10:02 ` Jeff King
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20210421200816.GA13772@dcvr \
--to=e@80x24.org \
--cc=git@vger.kernel.org \
/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.
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 NNTP newsgroup(s).