Re: git suggestion of fix to Amon

Or this:

http://git.661346.n2.nabble.com/Large-repo-and-pack-packsizelimit-td7523383.html

2013/8/1 Javier Juan Martínez Cabezón <[email protected]>

>
> Amon can this help?
>
> https://www.kernel.org/pub/software/scm/git/docs/git-pack-objects.html
>
> ¿And in particular this?
>
> --depth=<n>
>
> These two options affect how the objects contained in the pack are stored
> using delta compression. The objects are first internally sorted by type,
> size and optionally names and compared against the other objects within
> --window to see if using delta compression saves space. --depth limits the
> maximum delta depth; making it too deep affects the performance on the
> unpacker side, because delta data needs to be applied that many times to
> get to the necessary object. The default value for --window is 10 and
> --depth is 50.
>  --window-memory=<n>
>
> This option provides an additional limit on top of --window; the window
> size will dynamically scale down so as to not take up more than *<n>*bytes in memory. This is useful in repositories with a mix of large and
> small objects to not run out of memory with a large window, but still be
> able to take advantage of the large window for the smaller objects. The
> size can be suffixed with "k", "m", or "g". --window-memory=0 makes
> memory usage unlimited, which is the default.
>  --max-pack-size=<n>
>
> Maximum size of each output pack file. The size can be suffixed with "k",
> "m", or "g". The minimum size allowed is limited to 1 MiB. If specified,
> multiple packfiles may be created. The default is unlimited, unless the
> config variable pack.packSizeLimit is set.
>
>