From: Linus Torvalds <torvalds@linux-foundation.org>
To: bob <kranki@mac.com>
Cc: git@vger.kernel.org
Subject: Re: git packs
Date: Fri, 9 Nov 2007 22:53:24 -0800 (PST) [thread overview]
Message-ID: <alpine.LFD.0.999.0711092244080.15101@woody.linux-foundation.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0711092211250.15101@woody.linux-foundation.org>
On Fri, 9 Nov 2007, Linus Torvalds wrote:
>
> That said, I have worked with a 3GB pack-file (one of the KDE trial
> repos). That worked fine. But git does tend to want a *lot* of memory for
> really big repositories, so I suspect that if you actually work with 2GB+
> pack-files, you'll be wanting a 64-bit environment just because you'll be
> wanting more than 2GB of physical RAM in order to be able to access it
> efficiently.
Just double-checked. Yes, sirree. You definitely want 4GB+ if you are
cloning a 3GB git pack-file. The "git-pack-objects" phase not only is
going to walk all over the pack-file, it's going to add its own memory
footprint on top of that just keeping track of all the objects.
So I doubt 2GB+ pack-files are all that practical on 32-bit hosts. At
least not with the kind of performance behaviour *I* would accept.
(Of course, since git packs things pretty damn well, it would need to be a
really really big project to be a 2GB+ pack-file, or just contain a lot of
generally large non-deltable binary data file - one scenario where git
definitely doesn't work wonderfully well, although I doubt many other
SCM's do either..)
Linus
next prev parent reply other threads:[~2007-11-10 6:53 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-10 4:47 git packs bob
2007-11-10 5:13 ` Nicolas Pitre
2007-11-10 6:00 ` bob
2007-11-10 6:36 ` Luke Lu
2007-11-10 6:58 ` Linus Torvalds
2007-11-10 7:59 ` David Brown
2007-11-10 6:38 ` Linus Torvalds
2007-11-10 6:53 ` Linus Torvalds [this message]
2007-11-10 7:19 ` bob
2007-11-11 4:35 ` Nicolas Pitre
2007-11-12 2:53 ` bob
2007-11-12 4:21 ` Nicolas Pitre
2007-11-12 14:15 ` bob
2007-11-10 17:40 ` bob
2007-11-10 17:45 ` David Brown
2007-11-10 18:01 ` bob
2007-11-11 11:09 ` Derek Fawcus
2007-11-11 12:54 ` bob
2007-11-12 4:46 ` Martin Langhoff
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=alpine.LFD.0.999.0711092244080.15101@woody.linux-foundation.org \
--to=torvalds@linux-foundation.org \
--cc=git@vger.kernel.org \
--cc=kranki@mac.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).