From: Sebastien Binet <binet@cern.ch>
To: Jameson Graef Rollins <jrollins@finestructure.net>,
Notmuch developer list <notmuch@notmuchmail.org>
Subject: post-new [was: Re: query on a subset of messages ?]
Date: Mon, 9 Jul 2012 19:04:45 +0200 [thread overview]
Message-ID: <87r4sk3lxu.fsf@cern.ch> (raw)
In-Reply-To: <87wr2c3mtj.fsf@cern.ch>
[-- Attachment #1: Type: text/plain, Size: 2054 bytes --]
Sebastien Binet <binet@cern.ch> writes:
> Jamie,
>
> Jameson Graef Rollins <jrollins@finestructure.net> writes:
>
>> On Mon, Jul 09 2012, Sebastien Binet <binet@cern.ch> wrote:
>>> I was trying to reduce the I/O stress during my usual email
>>> fetching+tagging by writing a little program using the go bindings to
>>> notmuch.
>>>
>>> ie:
>>> db, status := notmuch.OpenDatabase(db_path,
>>> notmuch.DATABASE_MODE_READ_WRITE)
>>> query := db.CreateQuery("(tag:new AND tag:inbox)")
>>> msgs := query.SearchMessages()
>>> for _,msg := range msgs {
>>> tag_msg(msg, tagqueries)
>>> }
>>>
>>>
>>> where tagqueries is a subquery of the form:
>>> [
>>> {
>>> "Cmd": "+to-me",
>>> "Query": "(to:sebastien.binet@cern.ch and not tag:to-me)"
>>> },
>>> {
>>> "Cmd": "+sci-notmuch",
>>> "Query": "from:notmuch@notmuchmail.org or to:notmuch@notmuchmail.org or subject:notmuch"
>>> }
>>> ]
>>
>>
>> Hi, Sebastian. It's really hard for me to believe that this is much
>> faster than simply making the two tagging calls in full:
>>
>> notmuch tag +to-me -- tag:new and tag:inbox and (to:sebastien.binet@cern.ch and not tag:to-me)
>> notmuch tag +sci-notmuch -- tag:new and tag:inbox and from:notmuch@notmuchmail.org or to:notmuch@notmuchmail.org or subject:notmuch"
>>
>> After the first call the cache will be fresh, so the overhead should be
>> minimal. It looks to me you're looking in to this as a post-new hook.
>> I do pretty much the same thing, and with the above properly constructed
>> searches the tagging is super fast.
>
> well, of course I don't have just those two:
>
> $ grep -He "^tag_new " emacs/notmuch-lib/notmuch-tag.sh | wc -l
> 54
>
> also:
> $ du -hs mail-notmuch/.notmuch
> 2.9G mail-notmuch/.notmuch
>
> that said, most of the I/O wait seem to come from 'notmuch new' (after
> having dropped all fs caches.)
>
> ok, post-new hook it is then :)
hum... is post-new supposed to be run even if there is no new message ?
-s
[-- Attachment #2: Type: application/pgp-signature, Size: 197 bytes --]
next prev parent reply other threads:[~2012-07-09 17:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-09 8:25 query on a subset of messages ? Sebastien Binet
2012-07-09 15:55 ` Jameson Graef Rollins
2012-07-09 16:45 ` Sebastien Binet
2012-07-09 17:04 ` Sebastien Binet [this message]
2012-07-09 17:11 ` post-new [was: Re: query on a subset of messages ?] Jameson Graef Rollins
2012-07-09 17:37 ` Jani Nikula
2012-07-10 9:59 ` Sebastien Binet
2012-07-10 16:48 ` Jameson Graef Rollins
2012-07-10 13:16 ` Jani Nikula
2012-07-09 16:30 ` query on a subset of messages ? Austin Clements
2012-07-09 17:06 ` Sebastien Binet
2012-07-19 8:13 ` Sebastien Binet
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=87r4sk3lxu.fsf@cern.ch \
--to=binet@cern.ch \
--cc=jrollins@finestructure.net \
--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).