From: David Bremner <david@tethera.net>
To: Nils Dagsson Moskopp <nils@dieweltistgarnichtso.net>,
notmuch@notmuchmail.org
Subject: Re: notmuch-hello buffer slow doe to slow query
Date: Sat, 12 Apr 2014 12:41:11 -0300 [thread overview]
Message-ID: <87ppkm4ktk.fsf@zancas.localnet> (raw)
In-Reply-To: <874n20go84.fsf@dieweltistgarnichtso.net>
[-- Attachment #1: Type: text/plain, Size: 1095 bytes --]
Nils Dagsson Moskopp <nils@dieweltistgarnichtso.net> writes:
>
> mjw1009 can reproduce if the from-query contains an "@" and thinks the
> problem may be "something deeper down in notmuch (actually probably in
> xapian)".
My own experiments contradict that (see attached patch for a test to
run). The exact address is about twice as fast to count on both of my
machines, which matches the amount of I/O. FWIW, my SSD based laptop is
about 10x faster (compared to a similarly specced desktop with HD) for
both of them, which kindof reinforces how I/O bound this is.
Replacing 'count' with 'search' gives pretty similar relative behaviour,
although much slower since it seems to do about 10x I/O.
Finally after an initial "notmuch tag +fromlinus
from:torvalds@linux-foundation.org", "notmuch count tag:fromlinus" seems
to be about 5-10x faster than "notmuch count
from:torvalds@linux-foundation.org". So that might be a workaround for
some people.
To sum up, I think the underlying question is whether the amount of I/O
that count does can be reduced when using non-boolean query terms.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: 0001-WIP-new-performance-test-for-notmuch-count.patch --]
[-- Type: text/x-diff, Size: 1118 bytes --]
From d3fbbe7ac0a1fb5b5691674226a3a3d000e15a1c Mon Sep 17 00:00:00 2001
From: David Bremner <david@tethera.net>
Date: Sat, 12 Apr 2014 11:50:22 -0300
Subject: [PATCH] WIP: new performance test for notmuch count
Probably not suitable for production because of sudo
---
performance-test/T03-count.sh | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
create mode 100755 performance-test/T03-count.sh
diff --git a/performance-test/T03-count.sh b/performance-test/T03-count.sh
new file mode 100755
index 0000000..e74437e
--- /dev/null
+++ b/performance-test/T03-count.sh
@@ -0,0 +1,23 @@
+#!/bin/bash
+
+test_description='counting'
+
+. ./perf-test-lib.sh
+
+time_start
+
+for i in $(seq 1 10); do
+ echo 3 | sudo tee /proc/sys/vm/drop_caches
+ notmuch --version > /dev/null
+ time_run "from:torvalds@linux-foundation.org " \
+ "notmuch count from:torvalds@linux-foundation.org"
+
+ echo 3 | sudo tee /proc/sys/vm/drop_caches
+ notmuch --version > /dev/null
+
+ time_run "from:linux-foundation.org " \
+ "notmuch count from:linux-foundation.org"
+done
+
+
+time_done
--
1.9.1
prev parent reply other threads:[~2014-04-12 15:41 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-11 10:22 notmuch-hello buffer slow doe to slow query Nils Dagsson Moskopp
2014-04-12 15:41 ` David Bremner [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=87ppkm4ktk.fsf@zancas.localnet \
--to=david@tethera.net \
--cc=nils@dieweltistgarnichtso.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).