From: Kjetil Barvik <barvik@broadpark.no>
To: git@vger.kernel.org
Subject: git repack: --depth=100000 causing larger not smaler pack file?
Date: Tue, 17 Mar 2009 20:05:25 +0100 [thread overview]
Message-ID: <867i2ot1fu.fsf@broadpark.no> (raw)
aloha!
Yesterday I run the following command on the updated GIT respository:
git repack -adf --window=250000 --depth=100000
After 280 minutes or so it finished, but the strange thing was that
the resulting pack-file was larger than before. I had expected that
it should be smaler, or at least the same size as before.
kjetil git (my_next)$ ls -l .git/objects/pack/*
-r-------- 1 kjetil kjetil 2757280 2009-03-16 15:18 .git/objects/pack/pack-c5f15d5c48d6b3902a49046d7e8a8d717e167051.idx
-r-------- 1 kjetil kjetil 19961120 2009-03-16 15:18 .git/objects/pack/pack-c5f15d5c48d6b3902a49046d7e8a8d717e167051.pack
Before I started the pack file was around 19 250 000 bytes, and was
the result of the following commands:
1) git repack -adf --window=250000 --depth=20000
- not completly sure about the --window number here
- the resulting pack file was a litle less than 19 100 000
2) 'git fetch' to get the latest GIT patches
3) since 'git fetch' always make an extra new "smal" pack file, I run
the command 'git repack -ad --window=40000 --depth=10000' to be
able to get one singel pack file of 19 250 000 bytes or so.
I can think of one thing which is spesial with the "--depth=100000"
number, and that is that it is now larger than the total number of
objects in the pack, which is around 96000 to 97000, or so.
I have run 'git fsck --strict --full' on the pack with no resulting
error/debug output or change in the file size.
Any help on how to debug this?
-- kjetil
next reply other threads:[~2009-03-17 19:07 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-17 19:05 Kjetil Barvik [this message]
2009-03-17 20:38 ` git repack: --depth=100000 causing larger not smaler pack file? Nicolas Pitre
2009-03-23 10:11 ` Kjetil Barvik
2009-03-23 10:20 ` Mike Ralphson
2009-03-23 14:05 ` Peter Harris
2009-03-23 14:14 ` Nicolas Pitre
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=867i2ot1fu.fsf@broadpark.no \
--to=barvik@broadpark.no \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.