From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <cworth@cworth.org>
Received: from localhost (localhost [127.0.0.1])
	by olra.theworths.org (Postfix) with ESMTP id 5561A431FC0;
	Thu, 26 Nov 2009 10:47:09 -0800 (PST)
X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
Received: from olra.theworths.org ([127.0.0.1])
	by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id CB984xhn+xWR; Thu, 26 Nov 2009 10:47:08 -0800 (PST)
Received: from cworth.org (localhost [127.0.0.1])
	by olra.theworths.org (Postfix) with ESMTP id 8AA71431FAE;
	Thu, 26 Nov 2009 10:47:08 -0800 (PST)
From: Carl Worth <cworth@cworth.org>
To: Dominik Epple <dominik.epple@googlemail.com>
In-Reply-To: <123554aa0911250139l907c4efs60d704dae962c473@mail.gmail.com>
References: <123554aa0911200056h73def158pb0db64a2a78ed687@mail.gmail.com>
	<87skc8oqyn.fsf@yoom.home.cworth.org>
	<123554aa0911230826o11e54d5ckc90e5ae8dab6ffd3@mail.gmail.com>
	<123554aa0911250139l907c4efs60d704dae962c473@mail.gmail.com>
Date: Thu, 26 Nov 2009 10:46:54 -0800
Message-ID: <87y6ltqg2p.fsf@yoom.home.cworth.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Cc: notmuch@notmuchmail.org
Subject: Re: notmuch new: Memory problem
X-BeenThere: notmuch@notmuchmail.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Use and development of the notmuch mail system."
	<notmuch.notmuchmail.org>
List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
List-Archive: <http://notmuchmail.org/pipermail/notmuch>
List-Post: <mailto:notmuch@notmuchmail.org>
List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
	<mailto:notmuch-request@notmuchmail.org?subject=subscribe>
X-List-Received-Date: Thu, 26 Nov 2009 18:47:09 -0000

On Wed, 25 Nov 2009 10:39:57 +0100, Dominik Epple <dominik.epple@googlemail.com> wrote:
> So the problem stems indeed from too many too large files being
> present. (I actually found some being as large as 40M, not just 2.4M,
> as written in previous mails.)

That's very good to know.

And I'm glad you at least have things working smoothly now.

So perhaps the new configuration option we want is a limit on message
size? Rather than ignoring large files entirely, notmuch could just stop
indexing messages past the configured limit?

-Carl