From: martin f krafft <madduck@madduck.net>
To: "Aneesh Kumar K. V" <aneesh.kumar@linux.vnet.ibm.com>,
Ben Gamari <bgamari.foss@gmail.com>, Olly Betts <olly@survex.com>,
notmuch@notmuchmail.org
Subject: Re: Notmuch performance (literally, in my case)
Date: Thu, 28 Jul 2011 19:29:33 +0200 [thread overview]
Message-ID: <20110728172933.GA20173@fishbowl.rw.madduck.net> (raw)
In-Reply-To: <20100316180052.GA6600@piper.oerlikon.madduck.net>
[-- Attachment #1: Type: text/plain, Size: 1295 bytes --]
also sprach martin f krafft <madduck@madduck.net> [2010.03.16.1900 +0100]:
> I use ext4 with data=ordered, and while notmuch is writing the
> Xapian database, most I/O stalls on the machine:
>
> - Firefox does not get any mouse events
> - Vim blocks writing the viminfo file
> - All disk operations queue for multiple seconds.
>
> So no, ext4 is not a solution. Is it just me, or should no
> filesystem of this world be able to hog a system this badly? I think
> the culprit is the IO-scheduler.
I just wanted to send a little update on this. Even though the Linux I/O
scheduler performs abysmally during the Xapian database updates,
I can report two improvements, at least to my situation:
1. The 3.0 kernel seems to be better, but I did not quantify this
in any way, and I might just as well be wrong.
2. http://bugs.debian.org/635768 explains the (also I/O-related)
lockups we've seen. Micah offered the tip that the actual fault
lies with the awesome WM.
Cheers,
--
martin | http://madduck.net/ | http://two.sentenc.es/
"writing a book about debian
is like hitting a moving target
with a champagne bottle cork."
-- arky
spamtraps: madduck.bogus@madduck.net
[-- Attachment #2: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current) --]
[-- Type: application/pgp-signature, Size: 1124 bytes --]
prev parent reply other threads:[~2011-07-28 17:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-15 5:59 Notmuch performance (literally, in my case) Ben Gamari
2010-03-15 9:04 ` Hans Dieter Pearcey
2010-03-15 9:29 ` Olly Betts
2010-03-15 17:29 ` Ben Gamari
2010-03-16 11:08 ` Olly Betts
2010-03-16 15:37 ` Ben Gamari
2010-03-16 17:10 ` Aneesh Kumar K. V
2010-03-16 17:22 ` Ben Gamari
2010-03-16 18:00 ` martin f krafft
2010-03-16 19:18 ` Ben Gamari
2011-07-28 17:29 ` martin f krafft [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=20110728172933.GA20173@fishbowl.rw.madduck.net \
--to=madduck@madduck.net \
--cc=aneesh.kumar@linux.vnet.ibm.com \
--cc=bgamari.foss@gmail.com \
--cc=notmuch@notmuchmail.org \
--cc=olly@survex.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).