From: Hamish Downer <hamish@foobacca.co.uk>
To: Jani Nikula <jani@nikula.org>
Cc: notmuch@notmuchmail.org
Subject: Re: notmuch killed due to out of memory - how to move forward
Date: Tue, 4 Feb 2014 18:03:45 +0000 [thread overview]
Message-ID: <CAOxvSbcii-0YDs3+Q0=oJ6gMrbd5E59-FraPDJjvdaL3u2OCqw@mail.gmail.com> (raw)
In-Reply-To: <87r47jcmj6.fsf@nikula.org>
On 4 February 2014 08:25, Jani Nikula <jani@nikula.org> wrote:
> On Mon, 03 Feb 2014, Hamish Downer <hamish@foobacca.co.uk> wrote:
>> I recently deleted almost 30000 old messages from my maildirs, and
>> since I did that, notmuch new has not managed to complete. I have it
>> running on a server with 1 GB of RAM, and the output is telling me
>>
>> Cleaned up 25515 of 29803 messages (1m 10s remaining).
>>
>> at the point it is killed. I have followed it up to this point with
>> top and free and I can see memory usage growing to something like
>> 700MB (RES) at which point the process is killed.
>
> Please try SIGINT, or ^C, on notmuch new before it gets killed. That
> should be handled gracefully, making progress, and letting you chop up
> and eventually finish the operation. Please let us know if this helps.
That did it, thank you. Good to know Ctrl-C is gracefully handled.
> Needless to say, we shouldn't use that much memory just to delete files
> from the index.
I have saved a copy of the index from before I fixed the problem. I am
happy to re-run it with a rebuilt notmuch if that would be useful from the
point of view of uncovering bugs.
Otherwise I'll carry on as a happy notmuch user
Hamish
prev parent reply other threads:[~2014-02-04 18:04 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-03 22:18 notmuch killed due to out of memory - how to move forward Hamish Downer
2014-02-04 8:25 ` Jani Nikula
2014-02-04 9:01 ` Kushal Kumaran
2014-02-04 18:03 ` Hamish Downer [this message]
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: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAOxvSbcii-0YDs3+Q0=oJ6gMrbd5E59-FraPDJjvdaL3u2OCqw@mail.gmail.com' \
--to=hamish@foobacca.co.uk \
--cc=jani@nikula.org \
--cc=notmuch@notmuchmail.org \
/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://yhetil.org/notmuch.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).