Re: gcc git's performance problem Fwd: git gc expanding packed data?

[Hin-Tak Leung <hintak.leung@gmail.com>]

On Fri, Aug 7, 2009 at 1:49 PM, Frank Ch. Eigler<fche@redhat.com> wrote:
> Hi -
>
> Nicolas wrote:
>
>> Anyone has an idea of the git version running on gcc.gnu.org?  It is
>> certainly buggy and needs fixing.
>
> It was 1.6.3.2 now it's 1.6.4, practically spring chickens.
>
>> Anyway... To solve your problem, you simply need to run 'git gc' with
>> the --prune=now  [...]
>> And BTW, using 'git gc --aggressive' with a later git version (or
>> 'git repack -a -f -d --window=250 --depth=250') gives me a .git/objects
>> directory size of 310 MB [...]
>
> Unfortunately, git gc --aggressive / repack proceed consume several
> gigabytes of memory, which on the 32-bit host sometimes fails.
>
>
> - FChE
>

I have a bit more discussion with the git guys (see the git archive if
interested), apparently the loose objects are all the user, feature
and misc svn branches. I guess they are of some use to somebody. I
think git user intending to casually play with gcc (e.g. following the
development for a small period of a few weeks, etc to fix some bugs)
needs to know about this problem with git gc (blowing up the packed
objects to a few gigabyte) though.

Thanks anyhow.