git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: <randall.s.becker@rogers.com>
To: <git@vger.kernel.org>
Subject: [Question] clone performance
Date: Fri, 23 Aug 2019 21:59:14 -0400	[thread overview]
Message-ID: <005f01d55a1f$88e2ab20$9aa80160$@rogers.com> (raw)

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. I have tried to
convince them that their process is not reasonable and should stick with
existing clones, using branch checkout rather that re=cloning for each
feature branch. Sadly, I have not been successful - not for a lack of
trying. Is there any way to improve raw clone performance in a situation
like this, where status really doesn't matter, because the clone's life span
is under 48 hours.

TIA,
Randall



             reply	other threads:[~2019-08-24  1:59 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-24  1:59 randall.s.becker [this message]
2019-08-24 21:00 ` [Question] clone performance Bryan Turner
2019-08-26 14:16   ` randall.s.becker
2019-08-26 18:21     ` Jeff King
2019-08-26 19:27       ` Elijah Newren

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: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='005f01d55a1f$88e2ab20$9aa80160$@rogers.com' \
    --to=randall.s.becker@rogers.com \
    --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. 
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.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).