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

Benoit Boissinot benoit.boissinot at ens-lyon.org
Wed Jan 14 07:54:21 CST 2009


On Wed, Jan 14, 2009 at 01:37:21AM -0800, bughound 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.
> > 
> 
> The number of revisions is over 25,000.
> 
> .hg/store/00manifest.d is 2GB
> .hg/store/data directory is another 1GB

Could you send the .hg/store/00manifest.i file ? (it shouldn't be huge
and doesn't contain sensitive information, only the topology
information)

regards,

Benoit

-- 
:wq


More information about the Mercurial mailing list