hg out of memory

Martin Geisler mg at aragost.com
Tue Jun 14 05:24:13 CDT 2011

Luca <yelsma at tin.it> writes:

Hi Na'Tosha and hi Luca

> Il 11/06/2011 13.05, Na'Tosha Bard ha scritto:
>> As far as I know, there is no way to deal with large binaries in your
>> repository without using one of these tools. If you decide to try out
>> the HugeFiles extension, then please let me know. Of course
>> implementation of these solutions would also require that you get
>> your code out of subversion into a proper Mercurial repository.
>> As for whether the core Mercurial team plans to somehow address the
>> issue of large binary files internall, I don't kow -- someone with
>> more knowledge in that area would have to comment.

I'm afraid there is no immediate plan for adressing this in the core of
Mercurial: like you say, Mercurial fundamentally assumes that it can
load a complete file into memory to work on it.

> [...] My company has many bases (Italy, China, USA, ...) and now we
> can share the code and the binary files with a centralized svn server
> using https;

If the files are in many different locations in your working copy, then
the big/huge-files extensions are your best choice.

But if the large files are in a few subdirectories only, then perhaps
you would be happy with a Subversion subrepository. Mercurial lets you
include other repositories in your repo in a way very similar to the
svn:externals property in Subversion. Unlike Subversion, subrepos can be
of different types: Mercurial, Git, and Subversion subrepos.

This lets you include (part of) a Subversion repository in a Mercurial
checkout. When you do 'hg clone', then Mercurial will run the necessary
'svn checkout' commands for you automatically.

Please see the guide my company made:


Martin Geisler

aragost Trifork
Professional Mercurial support

More information about the Mercurial mailing list