Re: git-repack & big files

From: Pietro Battiston <me@pietrobattiston.it>
Date: Jan 11, 2011, 19:03 UTC
Message-ID: <1294772603.3435.67.camel@voubian.casa>
In-Reply-To: <4D2C7AA9.1020506@cfl.rr.com>

Il giorno mar, 11/01/2011 alle 10.43 -0500, Phillip Susi ha scritto:

Show 10 quoted lines

> On 1/11/2011 2:37 AM, Pietro Battiston wrote:
> > Since it perfectly does what it is not optimized to do... I then wonder
> > when it does not do what it declares: if I run git-repack² with the
> > parameter --window-memory set to, for instance, "100m", it takes
> > hundreds and hundreds of MB of memory until it runs out of memory, fails
> > a malloc and aborts.
> > So, two questions:
> 
> --window-memory reduces the window size to try and stay under the limit,
>  but the window size can not be reduced below 1.

OK, I think I understood. Still, I don't think there are many doubts that the documentation is misleading when it says "the window size will dynamically scale down so as to not take up more than N bytes in memory". That's all.

Show 7 quoted lines

> > 2) do I have any hope that in one way or another my 500+ MB mailboxes
> > with relatively small changes over time are archived smartly (=diffs) by
> > git at the current state of development? If I understand correctly, the
> > project git-bigfiles³ would just "solve" my problems by not making
> > differences of big files.
> 
> Git is not a backup tool.  You should use rsync rdiff-backup instead.

That's unfortunate - I think I prefer to split my mailboxes than to loose many of the nice features git provides. But thanks a lot for the suggestion.

Pietro