1 Return-Path: <cworth@cworth.org>
\r
2 X-Original-To: notmuch@notmuchmail.org
\r
3 Delivered-To: notmuch@notmuchmail.org
\r
4 Received: from localhost (localhost [127.0.0.1])
\r
5 by olra.theworths.org (Postfix) with ESMTP id 2470B431FBF;
\r
6 Fri, 20 Nov 2009 08:01:30 -0800 (PST)
\r
7 X-Virus-Scanned: Debian amavisd-new at olra.theworths.org
\r
8 Received: from olra.theworths.org ([127.0.0.1])
\r
9 by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)
\r
10 with ESMTP id hjGAfZFPtT5T; Fri, 20 Nov 2009 08:01:28 -0800 (PST)
\r
11 Received: from cworth.org (localhost [127.0.0.1])
\r
12 by olra.theworths.org (Postfix) with ESMTP id 5FFF9431FAE;
\r
13 Fri, 20 Nov 2009 08:01:28 -0800 (PST)
\r
14 From: Carl Worth <cworth@cworth.org>
\r
15 To: Dominik Epple <dominik.epple@googlemail.com>, notmuch@notmuchmail.org
\r
16 In-Reply-To: <123554aa0911200056h73def158pb0db64a2a78ed687@mail.gmail.com>
\r
17 References: <123554aa0911200056h73def158pb0db64a2a78ed687@mail.gmail.com>
\r
18 Date: Fri, 20 Nov 2009 17:01:17 +0100
\r
19 Message-ID: <877htlmbhu.fsf@yoom.home.cworth.org>
\r
21 Content-Type: text/plain; charset=us-ascii
\r
22 Subject: Re: [notmuch] notmuch new: Memory problem
\r
23 X-BeenThere: notmuch@notmuchmail.org
\r
24 X-Mailman-Version: 2.1.12
\r
26 List-Id: "Use and development of the notmuch mail system."
\r
27 <notmuch.notmuchmail.org>
\r
28 List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,
\r
29 <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>
\r
30 List-Archive: <http://notmuchmail.org/pipermail/notmuch>
\r
31 List-Post: <mailto:notmuch@notmuchmail.org>
\r
32 List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>
\r
33 List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,
\r
34 <mailto:notmuch-request@notmuchmail.org?subject=subscribe>
\r
35 X-List-Received-Date: Fri, 20 Nov 2009 16:01:30 -0000
\r
37 On Fri, 20 Nov 2009 09:56:50 +0100, Dominik Epple <dominik.epple@googlemail.com> wrote:
\r
38 > I am strongly interested in giving notmuch a try.
\r
40 Welcome to notmuch, Dominik! I'm sorry your initial attempt to use it
\r
41 hasn't been quite as smooth as we might like.
\r
43 > But I fail setting
\r
44 > it up. The problem is that during "notmuch new", memory consumption
\r
45 > and system load increases to values that make my system unusable. I
\r
46 > then killed "notmuch new" at a memory consumption of 2.7G and at a
\r
49 Yikes. That really sounds like something ran out of control consuming
\r
50 memory. I certainly haven't seen anything like that before.
\r
52 > After hitting Ctrl-C, it says "Stopping" but does not stop. I then
\r
53 > killed "notmuch new" after some minutes with signal KILL.
\r
55 After "Stopping" gets printed, the notmuch code won't be doing any more
\r
56 work. It is expected that it will take some time after that message is
\r
57 printed before notmuch will actually exit. The extra time is to wait for
\r
58 Xapian to flush out to disk data that notmuch has already provided to
\r
61 I'm curious how big your .notmuch directory ended up after this
\r
62 operation. (And how that compares in size to the total size of your
\r
63 collection of mail.)
\r
65 > Is there a problem with the number of my mails? I currently have over
\r
66 > 40.000 Mails... they live currently in mbox files, I created a Maildir
\r
67 > with mb2md-3.20.pl.
\r
69 That's definitely not too much mail. I think you should expect "notmuch
\r
70 new" currently to index on the order of 10 - 100 messages/sec.
\r
72 Your "notmuch new" process should have been reporting a count once per
\r
73 second as it progressed, (at least until things went wrong). How far did
\r
76 I'm wondering if there's a particular file (or files) that are
\r
77 triggering the bad behavior. Maybe we need a debug option for "notmuch
\r
78 new" to print the filenames of messages as they are being processed.
\r
projects / notmuch-archives.git / blob