git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: Removing old data without disturbing tree?

From
David Brown <git@davidb.org>
Date
Nov 27, 2007, 21:10 UTC
Message-ID
<20071127211006.GA22242@old.davidb.org>
In-Reply-To
<alpine.LFD.0.99999.0711271459520.9605@xanadu.home>
On Tue, Nov 27, 2007 at 03:06:45PM -0500, Nicolas Pitre wrote:
Show 18 quoted lines
>On Tue, 27 Nov 2007, David Brown wrote:
>
>> An upstream tree I'm mirroring with git-p4 has decided to start checking
>> in large tarballs (150MB) periodically.  It's basically a prebuild version
>> of some firmware needed to run the rest of the software.
>> 
>> Git doesn't seem to have any problem with these tarballs (and is using a
>> lot less space than P4), but I have a feeling we might start running into
>> problems when things get real big.  Does anyone have experience with packs
>> growing beyong several GB?
>
>It should just work.  It was tested with artificial data sets but that's 
>about it.
>
>Now if those tarballs are actually multiple revisions of the same 
>package, you might consider storing them uncompressed and let Git delta 
>compress them against each other which will produce an even more 
>significant space saving.

I did manage to talk them into leaving them uncompressed. But, they are large, and don't seem to delta compress all that well. Maybe as more come, the compression will be better.

I guess this will be a good test case... It will probably take months or even a year or so for the repo to get up to several GB.

David
Previous: Nicolas Pitre
Message 3 of 3 in “Removing old data without disturbing tree?”
  1. David BrownNov 27, 2007
  2. Nicolas PitreNov 27, 2007
  3. David BrownNov 27, 2007

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.