Re: [notmuch] Notmuch performance problems on OSX

diff --git a/35/ab44b0d7760d23a25e743e9a5cd2515e93a066 b/35/ab44b0d7760d23a25e743e9a5cd2515e93a066
new file mode 100644 (file)
index 0000000..b29e593
--- /dev/null
+++ b/35/ab44b0d7760d23a25e743e9a5cd2515e93a066
@@ -0,0 +1,89 @@
+Return-Path: <gmn-notmuch@m.gmane.org>\r
+X-Original-To: notmuch@notmuchmail.org\r
+Delivered-To: notmuch@notmuchmail.org\r
+Received: from localhost (localhost [127.0.0.1])\r
+       by olra.theworths.org (Postfix) with ESMTP id 0F3B3431FBC\r
+       for <notmuch@notmuchmail.org>; Tue,  9 Feb 2010 14:09:59 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.784\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.784 tagged_above=-999 required=5\r
+       tests=[AWL=-0.785, BAYES_50=0.001] autolearn=ham\r
+Received: from olra.theworths.org ([127.0.0.1])\r
+       by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024)\r
+       with ESMTP id mSxZGbnJEe0S for <notmuch@notmuchmail.org>;\r
+       Tue,  9 Feb 2010 14:09:58 -0800 (PST)\r
+Received: from lo.gmane.org (lo.gmane.org [80.91.229.12])\r
+       by olra.theworths.org (Postfix) with ESMTP id 3CD02431FAE\r
+       for <notmuch@notmuchmail.org>; Tue,  9 Feb 2010 14:09:58 -0800 (PST)\r
+Received: from list by lo.gmane.org with local (Exim 4.69)\r
+       (envelope-from <gmn-notmuch@m.gmane.org>) id 1NeyHM-0002Vk-9Q\r
+       for notmuch@notmuchmail.org; Tue, 09 Feb 2010 23:09:56 +0100\r
+Received: from ip-118-90-138-203.xdsl.xnet.co.nz ([118.90.138.203])\r
+       by main.gmane.org with esmtp (Gmexim 0.1 (Debian))\r
+       id 1AlnuQ-0007hv-00\r
+       for <notmuch@notmuchmail.org>; Tue, 09 Feb 2010 23:09:56 +0100\r
+Received: from olly by ip-118-90-138-203.xdsl.xnet.co.nz with local (Gmexim\r
+       0.1 (Debian)) id 1AlnuQ-0007hv-00\r
+       for <notmuch@notmuchmail.org>; Tue, 09 Feb 2010 23:09:56 +0100\r
+X-Injected-Via-Gmane: http://gmane.org/\r
+To: notmuch@notmuchmail.org\r
+From: Olly Betts <olly@survex.com>\r
+Date: Tue, 9 Feb 2010 22:09:31 +0000 (UTC)\r
+Lines: 30\r
+Message-ID: <slrnhn3n8t.3ls.olly@msgid.survex.com>\r
+References: <5641883d1001140730l22832715ld6bdc95c9938d314@mail.gmail.com>\r
+       <87d41ce0qf.fsf@yoom.home.cworth.org>\r
+       <5641883d1001181035j534d8f5cxc3b5b0db315ff290@mail.gmail.com>\r
+       <5641883d1002091246r41562e28ref69732cdc79d1f8@mail.gmail.com>\r
+X-Complaints-To: usenet@ger.gmane.org\r
+X-Gmane-NNTP-Posting-Host: ip-118-90-138-203.xdsl.xnet.co.nz\r
+User-Agent: slrn/pre1.0.0-11 (Linux)\r
+Sender: news <news@ger.gmane.org>\r
+Subject: Re: [notmuch] Notmuch performance problems on OSX\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+List-Id: "Use and development of the notmuch mail system."\r
+       <notmuch.notmuchmail.org>\r
+List-Unsubscribe: <http://notmuchmail.org/mailman/options/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=unsubscribe>\r
+List-Archive: <http://notmuchmail.org/pipermail/notmuch>\r
+List-Post: <mailto:notmuch@notmuchmail.org>\r
+List-Help: <mailto:notmuch-request@notmuchmail.org?subject=help>\r
+List-Subscribe: <http://notmuchmail.org/mailman/listinfo/notmuch>,\r
+       <mailto:notmuch-request@notmuchmail.org?subject=subscribe>\r
+X-List-Received-Date: Tue, 09 Feb 2010 22:09:59 -0000\r
+\r
+On 2010-02-09, Oliver Charles wrote:\r
+> I just upgraded to xapian-core HEAD and notmuch master tip today, in\r
+> desparation to get away from GMail. Sadly it's still taking at least\r
+> 0.7s to tag a single thread (with one message). I'm really eager to\r
+> solve this, could anyone give me any pointers on how I could go about\r
+> profiling it or finding the cause of this problem?\r
+\r
+The first thing to try is disabling use of F_FULLFSYNC.  You'll need to\r
+run this command in the xapian-core source tree to comment out the F_FULLFSYNC\r
+code:\r
+\r
+perl -pi -e 's/^#ifdef F_FULLFSYNC/#if 0/' backends/*/*_io.h\r
+\r
+Then run "make" and "make install".\r
+\r
+This makes you a bit more vulnerable to power failures, but no worse than\r
+a typical Unix system.  There's some background here:\r
+\r
+http://lists.apple.com/archives/Darwin-dev/2005/Feb/msg00072.html\r
+\r
+Assuming that helps, then (a) you have a workaround, and (b) we'll know for\r
+sure it is F_FULLFSYNC to blame.\r
+\r
+I've created a ticket for a change to Xapian which should help here, but\r
+not had a chance to work on it yet:\r
+\r
+http://trac.xapian.org/ticket/426\r
+\r
+Cheers,\r
+    Olly\r
+\r