From: Martin Geisler <mg@lazybytes.net>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: bazaar@lists.canonical.com, Harry Putnam <reader@newsguy.com>,
mercurial@selenic.com, git@vger.kernel.org
Subject: Re: About single user setup for lightweights
Date: Fri, 19 Mar 2010 10:53:55 +0100 [thread overview]
Message-ID: <87k4t81vt8.fsf@hbox.dyndns.org> (raw)
In-Reply-To: <32541b131003181913v7319d6a1ydd72c0177729dbf4@mail.gmail.com> (Avery Pennarun's message of "Thu, 18 Mar 2010 22:13:53 -0400")
[-- Attachment #1: Type: text/plain, Size: 863 bytes --]
Avery Pennarun <apenwarr@gmail.com> writes:
> git sucks at handling large binary files (>50 megs or so) unless you
> have boatloads of RAM. If your binary files are moderately sized (a
> few megs) then it'll probably be reasonably efficient. I don't know
> about hg and bzr for memory usage.
Mercurial also uses lots of RAM, way more than I had hoped. I did some
tests with this recently:
http://markmail.org/message/uxqtmmnkyimxse5b
They show a factor 3-6 blowup when working with a 256 MB file.
We don't really recommend storing such large files in Mercurial. Instead
we recommend storing the files outside of the tree, e.g., on a server
with a huge disk. The bfiles extension can do this:
http://mercurial.selenic.com/wiki/BfilesExtension
--
Martin Geisler
Fast and powerful revision control: http://mercurial.selenic.com/
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2010-03-19 9:54 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-19 1:53 About single user setup for lightweights Harry Putnam
2010-03-19 2:13 ` Avery Pennarun
2010-03-19 9:53 ` Martin Geisler [this message]
2010-03-19 17:14 ` Avery Pennarun
2010-03-19 4:01 ` Ben Finney
2010-03-19 14:08 ` Sitaram Chamarty
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87k4t81vt8.fsf@hbox.dyndns.org \
--to=mg@lazybytes.net \
--cc=apenwarr@gmail.com \
--cc=bazaar@lists.canonical.com \
--cc=git@vger.kernel.org \
--cc=mercurial@selenic.com \
--cc=reader@newsguy.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).