From: Elijah Newren <newren@gmail.com>
To: Jeff King <peff@peff.net>
Cc: randall.s.becker@rogers.com, Bryan Turner <bturner@atlassian.com>,
Git Users <git@vger.kernel.org>
Subject: Re: [Question] clone performance
Date: Mon, 26 Aug 2019 12:27:03 -0700 [thread overview]
Message-ID: <CABPp-BHHPBJLxV=_Y3Vu9cG1x1Vg-fdfadud9w5FA+aeAWTaKw@mail.gmail.com> (raw)
In-Reply-To: <20190826182134.GA23399@sigill.intra.peff.net>
On Mon, Aug 26, 2019 at 12:04 PM Jeff King <peff@peff.net> wrote:
>
> On Mon, Aug 26, 2019 at 10:16:48AM -0400, randall.s.becker@rogers.com wrote:
>
> > On August 24, 2019 5:00 PM, Bryan Turner wrote:
> > > On Fri, Aug 23, 2019 at 6:59 PM <randall.s.becker@rogers.com> wrote:
> > > >
> > > > Hi All,
> > > >
> > > > I'm trying to answer a question for a customer on clone performance.
> > > > They are doing at least 2-3 clones a day, of repositories with about
> > > > 2500 files and 10Gb of content. This is stressing the file system.
> > >
> > > Can you go into a bit more detail about what "stress" means? Using too
> > > much disk space? Too many IOPS reading/packing? Since you specifically
> > > called out the filesystem, does that mean the CPU/memory usage is
> > > acceptable?
> >
> > The upstream is BitBucket, which does a gc frequently. I'm not sure
> > any of this is relating to the pack structure. Git is spending most of
> > its time writing the large number of large files into the working
> > directory - it is stress mostly the disk, with a bit on the CPU
> > (neither is acceptable to the customer). I am really unsure there is
> > any way to make things better. The core issue is that the customer
> > insists on doing a clone for every feature branch instead of using
> > pull/checkout. I have been unable to change their mind - to this point
> > anyway.
>
> Yeah, at the point of checkout there's basically no impact from anything
> the server is doing or has done (technically it could make things worse
> for you by returning a pack with absurdly long delta chains or
> something, but that would be CPU and not disk stress).
>
> I doubt there's much to optimize in Git here. It's literally just
> writing files to disk as quickly as it can, and it sounds like disk
> performance is your bottleneck.
Well, if it's just checkout, Stolee's sparse-checkout series he just
posted may be of interest to them...once it's polished up and included
in git, of course.
prev parent reply other threads:[~2019-08-26 19:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-24 1:59 [Question] clone performance randall.s.becker
2019-08-24 21:00 ` Bryan Turner
2019-08-26 14:16 ` randall.s.becker
2019-08-26 18:21 ` Jeff King
2019-08-26 19:27 ` Elijah Newren [this message]
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='CABPp-BHHPBJLxV=_Y3Vu9cG1x1Vg-fdfadud9w5FA+aeAWTaKw@mail.gmail.com' \
--to=newren@gmail.com \
--cc=bturner@atlassian.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=randall.s.becker@rogers.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.
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).