From: Michal Sojka <sojkam1@fel.cvut.cz>
To: Darren McGuicken <mailing-notmuch@fernseed.info>,
Matthieu Lemerre <racin@free.fr>,
notmuch@notmuchmail.org
Subject: Re: [PATCH] How to improve the mail handling workflow?
Date: Mon, 15 Nov 2010 09:00:32 +0100 [thread overview]
Message-ID: <87zktbow2n.fsf@steelpick.2x.cz> (raw)
In-Reply-To: <87hbflwkmk.fsf@bookbinder.fernseed.info>
On Sat, 13 Nov 2010, Darren McGuicken wrote:
> On Sat, 13 Nov 2010 07:05:58 +0100, Michal Sojka <sojkam1@fel.cvut.cz> wrote:
> > I agree with you in that in many cases tags can be replaced by saved
> > searches. Last time I did it, i.e. used saved searches to distinguish
> > messages from different mailing lists, the result was that it took
> > very long time (something like 5 seconds) to show notmuch-hello
>
> Interesting, what Xapian backend are you using? I moved to chert after
> id:"87ocl1lut1.fsf@yoom.home.cworth.org" and my notmuch-hello with 15
> saved searches appears in a couple of seconds when freshly loaded,
> faster when switching back to it after use.
I use chert as well.
> That may well be slower than just tag searches but it's not yet at a
> threshold where I notice it. How many searches had you saved?
I had 45 (or so). I wanted two searches for every mailing list. One
"tag:inbox and (...)" and the second only "...".
>
> > Additionally, I compared the speed of command line searches for tags
> > and for the whole email addresses and even without the bug mentioned
> > above, the search for to: is usually slower than the search for tag:.
>
> Very non-scientifically just using time and vm/drop_caches on my
> netbook, having tagged all mail sent to the list address with 'notmuch',
> I seem to get much the same performance:
>
> $ time notmuch search tag:notmuch > /dev/null
>
> real 0m21.074s
> user 0m4.740s
> sys 0m1.916s
>
> $ time notmuch search to:notmuch > /dev/null
>
> real 0m20.280s
> user 0m4.600s
> sys 0m2.048s
>
> $ time notmuch search to:notmuch@notmuchmail.org > /dev/null
>
> real 0m21.790s
> user 0m5.044s
> sys 0m2.008s
My current numbers (with hot cache) are bellow.
$ time notmuch count tag:notmuch
3243
0,00s user 0,00s system 72% cpu 0,011 total
$ time notmuch count to:notmuch@notmuchmail.org
2477
0,03s user 0,00s system 89% cpu 0,036 total
That is 36ms vs. 11ms. If these numbers are multiplied by 45 (or by 90
with the bug in notmuch hello), this makes the difference.
-Michal
next prev parent reply other threads:[~2010-11-15 8:00 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-12 15:23 [PATCH] How to improve the mail handling workflow? Matthieu Lemerre
2010-11-12 15:33 ` Jameson Rollins
2010-11-12 16:39 ` Matthieu Lemerre
2010-11-14 21:07 ` Sebastian Spaeth
2010-11-14 21:19 ` Jameson Rollins
2010-11-14 21:31 ` Sebastian Spaeth
2010-11-15 8:28 ` David Edmondson
2010-11-12 15:39 ` Darren McGuicken
2010-11-12 16:35 ` Matthieu Lemerre
2010-11-12 16:58 ` Darren McGuicken
2010-11-14 21:34 ` Sebastian Spaeth
2010-11-14 23:25 ` Matthieu Lemerre
2010-11-13 6:05 ` Michal Sojka
2010-11-13 11:03 ` Darren McGuicken
2010-11-15 8:00 ` Michal Sojka [this message]
2010-11-12 17:05 ` David Edmondson
2010-11-12 17:48 ` Matthieu Lemerre
2010-11-12 17:42 ` David Edmondson
2010-11-13 16:43 ` Cédric Cabessa
2010-11-13 18:41 ` Jameson Rollins
2010-11-14 17:01 ` Matthieu Lemerre
2010-11-14 19:13 ` Jameson Rollins
2010-11-14 21:43 ` Matthieu Lemerre
2010-11-14 21:45 ` Michael Hudson
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=87zktbow2n.fsf@steelpick.2x.cz \
--to=sojkam1@fel.cvut.cz \
--cc=mailing-notmuch@fernseed.info \
--cc=notmuch@notmuchmail.org \
--cc=racin@free.fr \
/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).