From: David Abrahams <dave@boostpro.com>
To: Jeff King <peff@peff.net>
Cc: git@vger.kernel.org
Subject: Re: "malloc failed"
Date: Wed, 28 Jan 2009 19:06:28 -0500 [thread overview]
Message-ID: <87skn3rn5n.fsf@mcbain.luannocracy.com> (raw)
In-Reply-To: <c26bbb3fe074f6f6e0634a4ae8611239@206.71.190.141> (David Abrahams's message of "Wed, 28 Jan 2009 13:53:49 -0800")
on Wed Jan 28 2009, David Abrahams <dave-AT-boostpro.com> wrote:
> On Wed, 28 Jan 2009 00:02:25 -0500, Jeff King <peff@peff.net> wrote:
>> On Tue, Jan 27, 2009 at 10:04:42AM -0500, David Abrahams wrote:
>>
>>> I've been abusing Git for a purpose it wasn't intended to serve:
>>> archiving a large number of files with many duplicates and
>>> near-duplicates. Every once in a while, when trying to do something
>>> really big, it tells me "malloc failed" and bails out (I think it's
>>> during "git add" but because of the way I issued the commands I can't
>>> tell: it could have been a commit or a gc). This is on a 64-bit linux
>>> machine with 8G of ram and plenty of swap space, so I'm surprised.
>>>
>>> Git is doing an amazing job at archiving and compressing all this stuff
>>> I'm putting in it, but I have to do it a wee bit at a time or it craps
>>> out. Bug?
>>
>> How big is the repository? How big are the biggest files? I have a
>> 3.5G repo with files ranging from a few bytes to about 180M. I've never
>> run into malloc problems or gone into swap on my measly 1G box.
>> How does your dataset compare?
>
> I'll try to do some research. Gotta go pick up my boy now...
Well, moving the 2.6G .dar backup binary out of the fileset seems to
have helped a little, not surprisingly :-P
I don't know whether anyone on this list should care about that failure
given the level of abuse I'm inflicting on Git, but keep in mind that
the system *does* have 8G of memory. Conclude what you will from that,
I suppose!
--
Dave Abrahams
BoostPro Computing
http://www.boostpro.com
next prev parent reply other threads:[~2009-01-29 0:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-27 15:04 "malloc failed" David Abrahams
2009-01-27 15:29 ` Shawn O. Pearce
2009-01-27 15:32 ` David Abrahams
2009-01-27 18:02 ` Johannes Schindelin
2009-01-28 5:02 ` Jeff King
2009-01-28 21:53 ` David Abrahams
2009-01-29 0:06 ` David Abrahams [this message]
2009-01-29 5:20 ` Jeff King
2009-01-29 5:56 ` Jeff King
2009-01-29 7:53 ` Junio C Hamano
2009-01-29 13:10 ` David Abrahams
2009-01-29 13:41 ` Andreas Ericsson
2009-01-30 4:49 ` Jeff King
2009-01-28 22:16 ` Pau Garcia i Quiles
2009-01-29 5:14 ` Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87skn3rn5n.fsf@mcbain.luannocracy.com \
--to=dave@boostpro.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).