.hg directory has eclipsed 3GB - how to deal with huge manifest?

[Peter Arrenbrecht]

On Wed, Jan 14, 2009 at 10:37 AM, bughound <bughound at gmail.com> wrote:
>
>
> Patrick Mézard wrote:
>>
>> bughound a écrit :
>>> As our project has progressed, so has the manifest (.hg directory).
>>>
>>> It's now over 3GB and causing anyone who wants to clone a new area a
>>> 20-minute wait while the .hg directory gets populated over our network.
>>>
>>> What's the recommended way for resetting this?
>>>
>>> One would think it should be fairly straightforward to archive this
>>> manifest
>>> off somewhere else and start it from scratch periodically...
>>
>> By curiosity, can you give some numbers about your project like the number
>> of revisions, the size of the manifest, etc... An estimate of the ratio of
>> merge revisions over total revisions would be interesting too.
>>
>> --
>> Patrick Mézard
>> _______________________________________________
>> Mercurial mailing list
>> Mercurial at selenic.com
>> http://selenic.com/mailman/listinfo/mercurial
>>
>>
>
> The number of revisions is over 25,000.
>
> .hg/store/00manifest.d is 2GB
> .hg/store/data directory is another 1GB

Maybe a hg->hg conversion with topological sorting of commits would
help a bit. Depends on the interleaving of commits to separate heads
in the repo.

In the longer run, shallow cloning might help. This is a
work-in-progress that is not currently usable, though.

-parren