Date: Thu, 28 Jul 2011 19:29:33 +0200
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] Notmuch performance (literally, in my case)
Message-ID: <20110728172933.GA20173@fishbowl.rw.madduck.net>
Mail-Followup-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
References: <4b9dccc0.c6c1f10a.3671.44ec@mx.google.com>
	<20100315090401.GA29891@glaive.weftsoar.net>
	<slrnhprvfv.hu6.olly@msgid.survex.com>
	<4b9e6e80.09b6660a.6769.6832@mx.google.com>
	<20100316110846.GK10323@survex.com>
	<4b9fa5d2.0a4d5e0a.0c0b.ffffdcbb@mx.google.com>
	<87mxy8chvq.fsf@linux.vnet.ibm.com>
	<20100316180052.GA6600@piper.oerlikon.madduck.net>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
	protocol="application/pgp-signature"; boundary="/04w6evG8XlLl3ft"
Content-Disposition: inline
In-Reply-To: <20100316180052.GA6600@piper.oerlikon.madduck.net>
User-Agent: Mutt/1.5.21 (2010-09-15)
Precedence: list


--/04w6evG8XlLl3ft
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

also sprach martin f krafft <madduck@madduck.net> [2010.03.16.1900 +0100]:
> I use ext4 with data=3Dordered, and while notmuch is writing the
> Xapian database, most I/O stalls on the machine:
>=20
>   - Firefox does not get any mouse events
>   - Vim blocks writing the viminfo file
>   - All disk operations queue for multiple seconds.
>=20
> 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,

--=20
martin | http://madduck.net/ | http://two.sentenc.es/
=20
"writing a book about debian
 is like hitting a moving target
 with a champagne bottle cork."
                                                             -- arky
=20
spamtraps: madduck.bogus@madduck.net

--/04w6evG8XlLl3ft
Content-Type: application/pgp-signature; name="digital_signature_gpg.asc"
Content-Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current)

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)

iQLvBAEBCgDZBQJOMZx9wBEaaHR0cDovL21hcnRpbi1rcmFmZnQubmV0L2dwZy9z
aWctcG9saWN5LzU1Yzk4ODJkOTk5YmJjYzQvMjAxMTAxMjQxMTI1P3NoYTUxMnN1
bT0xY2FkOTZmZDI3ZDMyMzNmNTNlMjI4NDk1MzM2NDgxMDdlNWVlOGQ1YmU2NTUy
NTFkNzRjOGYxYzVjM2JjNDJmMjMwNGZhNTE1MTUwZjdiZDRkZDA1ZTk4MTk5MjRm
MDQ5NTEzZWU5OTYyY2E3MTcwOWY4MWQ5NDUxNTg1MmJkOAAKCRBVyYgtmZu8xDgf
EAC58AitiSPQD49J+TpkeELYiU1f9X0A7Rg6uSzvG5i2aEJhILp1YIBUC4UivP8m
Yx49N4m0FpQl9Q7NscWiY+QczOm25WLpgn6TLOL2cD3fUhsYBxHeolZ50XW3RYLv
uL5YvzkeJUTWzyF9cNCZAQVfm1p5lGngJsQkYwq95KWFIsgo3SHb2/o9yM70Kgpe
PhWZcQKT6UQYxBpMuh2SgvzwG6d2Cie1u8bxu2zVAxlAmirD/GzJVwmgvOcP38SF
tO8ezKsoWGFDA0hzk2LF5JClYgjA7zx8UA4SB0EpplSr/lKbmsUyzp0atspK66rc
jsVQKWxg5ePeSw/9Aok0ChbkJtjON+rx0OyKmB9l0CLZ08JfZOtCiqKnZrTQGqYj
SEdu/AHEGt4R9zAiCN4VNuNpLzc8vrVLIVt9O8r+Iucwqi6qOgfeX2KQOIpiDiaV
blQHzgPMsfpUcUTVIgTrTHp/tuOnPuWy3mD+FRfIM8BRONn/gfPQcZjueIc7YO3r
pxUnIKVyYn7ktfd3lNrefkqq9OCan4bS91tepdRVBQ7m97utlDPWgRTExNG8331R
sjUsG7qCLDovB/rywAAGzguhzYkR9Voqe3uwuHPBISQqvxRMS/IugJ6ZTGqSFnyp
6pOVyD6u/pjqHQYbogOg8eBMG/3Govufb4hVcIAPVlSzUw==
=v/lU
-----END PGP SIGNATURE-----

--/04w6evG8XlLl3ft--