Space savings: cherry picking, partial cloning, overlays, history trimming, offline revisions, and obliterate

Matt Mackall mpm at
Fri Mar 21 14:36:08 CDT 2008

On Fri, 2008-03-21 at 12:14 -0700, Jared Hardy wrote:
> On Fri, Mar 21, 2008 at 6:19 AM, Martin Gadbois
> <martin.gadbois at> wrote:
> >  I like Mercurial, but I ran into this warning on some occasions, and I
> >  do not know if your images and other binary data could be affected:
> >
> >  $ hg add linux-2.4.32.tar.bz2
> >  linux-2.4.32.tar.bz2: files over 10MB may cause memory and performance
> >  problems
> >  (use 'hg revert linux-2.4.32.tar.bz2' to unadd the file)
> Oh yes, we go over 10MB files routinely. Is there any configuration
> setting to set the threshold higher? We would probably bump that up to
> a few hundred MB, in our use case. This is where Forest seems very
> handy, where we might have a normal code repository, in the same
> forest tree with a big art repository, each with different threshold
> warning settings.

It's just a warning, and the number is arbitrary. 10MB files may present
trouble on machines with, say, 64MB of memory, which is not uncommon for
virtual servers.

>     Do you know, does this size refer to the actual file, or the
> snapshot/diff size? Most of our files are diff-able, because they are
> raw uncompressed, so that may help temper this issue.

It applies to the actual file. Doing delta storage efficiently means
having two full revisions in memory and a fair amount of scratch space.

Mathematics is the supreme nostalgia of our time.

More information about the Mercurial mailing list