From: David Bremner <bremner@unb.ca>
To: Petter Reinholdtsen <pere@hungry.com>, notmuch@notmuchmail.org
Subject: Re: 'notmuch new' leaking memory and getting slower over time?
Date: Mon, 10 Dec 2012 07:50:09 -0400 [thread overview]
Message-ID: <87hanup1n2.fsf@zancas.localnet> (raw)
In-Reply-To: <2flfwhht87d.fsf@diskless.uio.no>
Petter Reinholdtsen <pere@hungry.com> writes:
> Running 'notmuch restore' to get my tags back took 106 minutes, and I
> was very surprised that the restore could not load all the tags stored
> by 'notmuch dump'. The restore complained about this line:
>
> NO*TELEMAX**NORWAYII M0018001012307699038 (unread usit year-2002)
>
> The message in question is a bounce from some X400 mail system, and its
> message id look like this:
>
> Message-Id: <NO*TELEMAX**NORWAYII M0018001012307699038>
>
> I would like 'notmuch new' to use less memory and be better at
> estimating the time left, and would also like 'notmuch restore' to
> always be able to load the output from 'notmuch dump'.
As of git commit 0.14-162-g5c7990f, notmuch supports a new dump restore
format 'batch-tag' that can handle these message-id's. See the man
pages for more details.
I'm marking this bug as fixed; feel free to let us know of any problems
with the new batch-tag format.
d
next prev parent reply other threads:[~2012-12-10 11:50 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-21 22:35 'notmuch new' leaking memory and getting slower over time? Petter Reinholdtsen
2011-11-22 21:50 ` David Bremner
2011-11-23 2:48 ` Austin Clements
2012-12-10 11:50 ` David Bremner [this message]
2012-12-10 12:39 ` David Bremner
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=87hanup1n2.fsf@zancas.localnet \
--to=bremner@unb.ca \
--cc=notmuch@notmuchmail.org \
--cc=pere@hungry.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.
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).