From: Theodore Tso <tytso@mit.edu>
To: Bill Lear <rael@zopyra.com>
Cc: git@vger.kernel.org
Subject: Re: Optimizing repository speed
Date: Mon, 19 Feb 2007 10:14:10 -0500 [thread overview]
Message-ID: <20070219151410.GG25490@thunk.org> (raw)
In-Reply-To: <17881.46642.843674.49482@lisa.zopyra.com>
On Mon, Feb 19, 2007 at 08:37:38AM -0600, Bill Lear wrote:
> As part of our conversion to git 1.5, I would like to ensure that
> our code repository does not get crufty and slow. Currently, I have
> a cron job that runs each morning that does a 'git repack -a -d'.
>
> I know there is 'git-gc', and it appears to do all sorts of good
> things. Can I simply replace my call to 'git repack -d -a' with 'git
> gc', or is there anything else I might want to do?
git-gc is a strict superset of git repack -a -d. Specifically, what
it does is:
git-pack-refs --prune
git-reflog expire --al
git-repack -a -d -l
git-rerere gc
It will also through in a git-prune if you do add --prune to the
git-gc call, but you really don't want to run that out of a cron job.
Regards,
- Ted
prev parent reply other threads:[~2007-02-19 15:14 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-19 14:37 Optimizing repository speed Bill Lear
2007-02-19 15:14 ` Theodore Tso [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=20070219151410.GG25490@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=rael@zopyra.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).