From: Marc Branchaud <mbranchaud@xiplink.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Felix Natter <fnatter@gmx.net>, git@vger.kernel.org
Subject: Re: git repack vs git gc --aggressive
Date: Mon, 13 Aug 2012 10:20:15 -0400 [thread overview]
Message-ID: <50290D1F.20007@xiplink.com> (raw)
In-Reply-To: <7v393ujypq.fsf@alter.siamese.dyndns.org>
On 12-08-10 04:09 PM, Junio C Hamano wrote:
> Felix Natter <fnatter@gmx.net> writes:
>
>> I have a few questions about this:
>>
>>> As I am coming from "large depth is harmful" school, I would
>>> recommend
>>>
>>> - "git repack -a -d -f" with large "--window" with reasonably short
>>> "--depth" once,
>>
>> So something like --depth=250 and --window=500?
>
> I would use more like --depth=16 or 32 in my local repositories.
>
>>> and mark the result with .keep;
>>
>> I guess you refer to a toplevel '.keep' file.
>
> Not at all. And it is not documented, it seems X-<.
>
> Typically you have a pair of files in .git/objects/pack, e.g.
>
> .git/objects/pack/pack-2e3e3b332b446278f9ff91c4f497bc6ed2626d00.idx
> .git/objects/pack/pack-2e3e3b332b446278f9ff91c4f497bc6ed2626d00.pack
>
> And you can add another file next to them
>
> .git/objects/pack/pack-2e3e3b332b446278f9ff91c4f497bc6ed2626d00.keep
>
> to prevent the pack from getting repacked. I think "git clone" does
> this for you after an initial import.
1.7.12.rc1 does not.
I even cloned from a repo with a few .keep files, but ended up with only one
big .pack file.
Maybe clone should preserve the packs it gets from the upstream repo? For
example, our main repo has a 690MB pack file that's marked .keep, but the
clone just ends up with a single 725MB pack file. Would our clones see
performance improvements if they that big 690MB pack separate from the others?
Perhaps the fact that clone creates a single pack file makes it impossible to
preserve the .keep packs from the upstream?
(I figure it's probably not a good idea for clone to .keep the single pack
file it creates.)
M.
next prev parent reply other threads:[~2012-08-13 14:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-07 18:22 git repack vs git gc --aggressive Felix Natter
2012-08-07 18:44 ` Jeff King
2012-08-07 19:05 ` Junio C Hamano
2012-08-10 19:09 ` Felix Natter
2012-08-10 20:09 ` Junio C Hamano
2012-08-13 14:20 ` Marc Branchaud [this message]
2012-08-13 17:19 ` Junio C Hamano
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=50290D1F.20007@xiplink.com \
--to=mbranchaud@xiplink.com \
--cc=fnatter@gmx.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=marcnarc@xiplink.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).