From: Pieter Praet <pieter@praet.org>
To: Xavier Maillard <xma@gnu.org>,
Florian Friesdorf <flo@chaoflow.net>,
notmuch@notmuchmail.org
Subject: Re: notmuch painfully slow
Date: Sun, 24 Apr 2011 10:13:49 +0200 [thread overview]
Message-ID: <87mxjgcbia.fsf@A7GMS.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <m24o5pzb56.fsf@gnu.org>
On Sat, 23 Apr 2011 07:18:52 +0200, Florian Friesdorf <flo@chaoflow.net> wrote:
> [...]
> Is this the switch from xapian 1.0.x to 1.2.x or are further steps
> necessary?
>
> Are there instructions on how to do the switch? For the mailing list
> archive a link would be great - a quick search for 'xapian flint chert'
> was unsuccessful.
>
> In case there are no instructions yet, I'm happy to conclude what is
> gathered here and add it to notmuch's webpage.
>
> --
> Florian Friesdorf <flo@chaoflow.net>
> GPG FPR: 7A13 5EEE 1421 9FC2 108D BAAF 38F8 99A3 0C45 F083
> Jabber/XMPP: flo@chaoflow.net
> IRC: chaoflow on freenode,ircnet,blafasel,OFTC
Non-text part: application/pgp-signature
On Sat, 23 Apr 2011 09:20:53 +0200, Xavier Maillard <xma@gnu.org> wrote:
> [...]
> Obviously, no, I did not. I even did not know about that ;) What's the
> story with this and what's the way to do this exactly ?
>
> Thank you.
>
> /Xavier
Both Carl [1] and Sebastian [2] posted about this a little while ago.
Bottom line: Chert is the new db format (replacing Flint) as of Xapian
1.2.x [3], and should -in most cases- be alot faster, whilst consuming
less disk space.
If .notmuch/xapian contains a file called "iamflint", you're still on
the old format. Otherwise it's called (surprise) "iamchert". Perhaps
somewhat confusingly, "flintlock" remains though.
Switching your notmuch db is straightforward:
>> notmuch dump ${tagdump}
>> rm -rf .notmuch/xapian
>> notmuch new
>> notmuch restore ${tagdump}
>> mv .notmuch/xapian .notmuch/xapian-fat
>> xapian-compact --no-renumber .notmuch/xapian-fat .notmuch/xapian
>> rm -rf .notmuch/xapian-fat
The last 3 lines are entirely optional and will cause writes to be a
bit more expensive in the short term, but will significantly reduce
the db's size, which your SSD will surely appreciate.
Peace
-Pieter
[1] id:"87ocl1lut1.fsf@yoom.home.cworth.org"
[2] id:"87lj0iqa3c.fsf@SSpaeth.de"
[3] http://www.archlinux.org/packages/?q=xapian-core
next prev parent reply other threads:[~2011-04-24 8:13 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-22 14:14 notmuch painfully slow Xavier Maillard
2011-04-22 20:18 ` Pieter Praet
2011-04-23 5:18 ` Florian Friesdorf
2011-04-23 6:41 ` Simon Fondrie-Teitler
2011-04-23 7:20 ` Xavier Maillard
2011-04-24 8:13 ` Pieter Praet [this message]
2011-04-26 20:04 ` Florian Friesdorf
2011-05-05 21:55 ` Xavier Maillard
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=87mxjgcbia.fsf@A7GMS.i-did-not-set--mail-host-address--so-tickle-me \
--to=pieter@praet.org \
--cc=flo@chaoflow.net \
--cc=notmuch@notmuchmail.org \
--cc=xma@gnu.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).