Re: Synchronization success stories?

diff --git a/a5/e7bc70acb452ab4200515e34c9d16d75a28075 b/a5/e7bc70acb452ab4200515e34c9d16d75a28075
new file mode 100644 (file)
index 0000000..900bdb4
--- /dev/null
+++ b/a5/e7bc70acb452ab4200515e34c9d16d75a28075
@@ -0,0 +1,97 @@
+Return-Path:\r
+ <return-2deyg6wba3x6j2jhvku4s4gc2i@temporary-address.scs.stanford.edu>\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 4B094431FBD\r
+       for <notmuch@notmuchmail.org>; Sun, 13 Apr 2014 08:23:46 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -2.3\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-2.3 tagged_above=-999 required=5\r
+       tests=[RCVD_IN_DNSWL_MED=-2.3] autolearn=disabled\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 ZwdBmnbyIqoq for <notmuch@notmuchmail.org>;\r
+       Sun, 13 Apr 2014 08:23:42 -0700 (PDT)\r
+Received: from market.scs.stanford.edu (market.scs.stanford.edu [171.66.3.10])\r
+       (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id 9E0C4431FBC\r
+       for <notmuch@notmuchmail.org>; Sun, 13 Apr 2014 08:23:42 -0700 (PDT)\r
+Received: from market.scs.stanford.edu (localhost.scs.stanford.edu\r
+ [127.0.0.1])  by market.scs.stanford.edu (8.14.7/8.14.7) with ESMTP id\r
+ s3DFNd5m017263;       Sun, 13 Apr 2014 08:23:39 -0700 (PDT)\r
+Received: (from dm@localhost)\r
+       by market.scs.stanford.edu (8.14.7/8.14.7/Submit) id s3DFNc9s000555;\r
+       Sun, 13 Apr 2014 08:23:38 -0700 (PDT)\r
+X-Authentication-Warning: market.scs.stanford.edu: dm set sender to\r
+       return-2deyg6wba3x6j2jhvku4s4gc2i@ta.scs.stanford.edu using -f\r
+From: David Mazieres <dm-list-email-notmuch@scs.stanford.edu>\r
+To: Tilmann Singer <tils@tils.net>, Brian Sniffen <bsniffen@akamai.com>,\r
+       notmuch@notmuchmail.org\r
+Subject: Re: Synchronization success stories?\r
+In-Reply-To: <87ppklwin6.fsf@tils.net>\r
+References: <m2r455f270.fsf@usma1mc-0csx92.kendall.corp.akamai.com>\r
+       <87ppklwin6.fsf@tils.net>\r
+Date: Sun, 13 Apr 2014 08:23:38 -0700\r
+Message-ID: <87siphl0cl.fsf@ta.scs.stanford.edu>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain\r
+X-BeenThere: notmuch@notmuchmail.org\r
+X-Mailman-Version: 2.1.13\r
+Precedence: list\r
+Reply-To: David Mazieres expires 2014-07-12 PDT\r
+       <mazieres-mbfu29xw9bpzdfpkk2m9i6pui2@temporary-address.scs.stanford.edu>\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: Sun, 13 Apr 2014 15:23:46 -0000\r
+\r
+Tilmann Singer <tils@tils.net> writes:\r
+\r
+> The steps performed on a sync run are roughly like this:\r
+>\r
+> - local: notmuch new\r
+> - local: notmuch search --output=messages <some time ago>..<now>\r
+> - remote: notmuch new\r
+> - remote: notmuch search --output=messages <some time ago>..<now>\r
+> - compare search results\r
+> - run rsync for mails that only exist locally\r
+>   (using notmuch search --output=files to get the filenames)\r
+> - run rsync for mails that only exist remotely\r
+>   (using notmuch search --output=files to get the filenames)\r
+\r
+What happens if you get a message that's been stuck in a queue for a few\r
+days and has an old Date: header?  Or if you get new messages that have\r
+the same Message-ID as old ones?\r
+\r
+> Synchronization of the notmuch tags database is only necessary when I\r
+> switch between different client computers, which happens less\r
+> frequently.\r
+\r
+Do you use a laptop everywhere?  I've found that for switching between\r
+my desktop machine at home, my laptop on the train, and my desktop at\r
+work (which amounts to five switches a day), the notmuch dump time is\r
+painfully slow--like well over 10 seconds for 100,000 messages.  Hook\r
+that into notmuch-poll and you have a recipe for hanging emacs every\r
+time you type "G".\r
+\r
+Of course, I'm also experiencing the problem of "notmuch new" itself\r
+being painfully slow, but at least that's now my bottleneck in switching\r
+machines.  I suspect the source of the notmuch new problem is that I\r
+have some huge, huge mailboxes.  Some of my maildir/cur directories are\r
+multiple megabytes on a BSD FFS file system (no hashing, so linear\r
+filename lookups in something that doesn't fit in the dcache).  On linux\r
+ext4 things are much faster.  I intend to reorganize my maildir so that\r
+there is a top-level directory with the year and hence no single\r
+directory ever contains mail from more than one year.\r
+\r
+David\r