Re: Fwd: tag storage format

Hi Michael,
I converted a repository and ran "git gc --prune=now" and ended up with
5.41GB. I ran the command again immediately afterwards and got 1.96GB.
Either its due to --aggressive or further improvement from running the
command twice instead of once? Anyway, definitely an improvement!

Uri

On Wed, Oct 24, 2012 at 2:25 AM, Michael Haggerty <[email protected]>wrote:

> [I'm adding CC to the mailing list, because these conversations might
> help other people and/or others might have something to contribute.]
>
> On 10/24/2012 08:00 AM, Uri Moszkowicz wrote:
> > Sorry to bother you again but apparently also need "git prune" or "git
> > gc --aggressive --prune=now". It seems that hoards of object files are
> > left around outside of the packs and "git gc" doesn't collect them
> > unless you specify it.
>
> I had already included "--prune=now".
>
> The use of --aggressive is controversial, at least in many
> circumstances.  It uses far more resources than "git gc" without
> --aggressive, and I believe it often takes hours or fails to complete
> due to lack of memory.  It supposedly doesn't usually help much either,
> at least in day-to-day git usage, and can even hurt.
>
> Of course a repository created from a cvs2git conversion and "git
> fast-import" is not typical, so we shouldn't discount --aggressive out
> of hand.  Have you done a comparison of "git gc --prune=now" vs. "git gc
> --prune=now --aggressive" on your repo?  What are the differences in
> runtime and in the size of the resulting repository?
>
> Michael
>
> --
> Michael Haggerty
> [email protected]
> http://softwareswirl.blogspot.com/
>

------------------------------------------------------
http://cvs2svn.tigris.org/ds/viewMessage.do?dsForumId=1670&dsMessageId=3023968

To unsubscribe from this discussion, e-mail: [[email protected]].