Return-Path: X-Original-To: notmuch@notmuchmail.org Delivered-To: notmuch@notmuchmail.org Received: from localhost (localhost [127.0.0.1]) by olra.theworths.org (Postfix) with ESMTP id E9942431FBC for ; Tue, 10 Jun 2014 15:13:10 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at olra.theworths.org X-Spam-Flag: NO X-Spam-Score: 0 X-Spam-Level: X-Spam-Status: No, score=0 tagged_above=-999 required=5 tests=[none] autolearn=disabled Received: from olra.theworths.org ([127.0.0.1]) by localhost (olra.theworths.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id C2M+11-XY9Yw for ; Tue, 10 Jun 2014 15:13:06 -0700 (PDT) X-Greylist: delayed 529 seconds by postgrey-1.32 at olra; Tue, 10 Jun 2014 15:13:06 PDT Received: from master.diplodocus.org (master.diplodocus.org [50.247.106.229]) by olra.theworths.org (Postfix) with ESMTP id 22AAE431FAF for ; Tue, 10 Jun 2014 15:13:06 -0700 (PDT) Received: from wundagore (localhost [127.0.0.1]) by master.diplodocus.org (Postfix) with ESMTP id 44EECFB4715; Tue, 10 Jun 2014 15:04:17 -0700 (PDT) From: Eric Gillespie To: notmuch@notmuchmail.org Subject: nmh + notmuch: expected to work? X-Mailer: MH-E 8.3.1; nmh 1.6-RC3; GNU Emacs 24.3.1 MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-ID: <24055.1402437857.1@wundagore> Content-Transfer-Encoding: quoted-printable Date: Tue, 10 Jun 2014 15:04:17 -0700 Message-ID: <24056.1402437857@wundagore> X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.13 Precedence: list List-Id: "Use and development of the notmuch mail system." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 10 Jun 2014 22:13:11 -0000 I'm a long-time nmh user, and I heard notmuch was supposed to handle mh folders, so I gave it a shot. It's crazy slow. The first 'notmuch new' took 4 hours, but maybe that's expected. However, every 'notmuch new' takes 4 - 10 hours. The only time it completes faster is if I immediately re-run it without incorporating new mail. In that case, it completes in 0.8s - 38s, which is quite reasonable for my mail. I have 18.5 GB, 1,058,370 messages in 315 directories. =46rom the messages it prints, apparently any directory that changes (receives a new message) has to have all its files indexed from scratch. What?! # re-index after some new mail (< 1000; not 704083!) Processed 704083 total files in 11h 7m 48s (17 files/sec.). Added 701791 new messages to the database. Removed 701332 messages. Detect= ed 2136 file renames. # re-index again, no new mail Processed 60 total files in 40s (1 files/sec.). No new mail. # incorporate 1 new message Processed 9181 total files in 7m 54s (19 files/sec.). Added 9071 new messages to the database. Removed 9071 messages. Detected 1= 2 file renames. # incorporate 1 new message Processed 111 total files in almost no time. Added 1 new message to the database. Detected 12 file renames. # incorporate 1 new message Processed 757 total files in 44s (17 files/sec.). Added 645 new messages to the database. Removed 645 messages. Detected 14 = file renames. There haven't been any renames at all, so I don't know what 2136, 12, or 14 renames notmuch is talking about. I wasn't reading or replying to any mail at all, only adding new mail and running notmuch new. I already thought mairix was slow, but in comparison, it's blazing fast. I think notmuch indexes much more so the comparison is not entirely fair, but at least it's usable. mairix takes 1h15m to process the same mail from scratch. Subsequent updates take from 19-22s. Also the mairix db is much smaller, though notmuch's is about the size the documentation says to expect: 0 ~% du -ms .mairix mh/.notmuch 447 .mairix 15712 mh/.notmuch Is this expected? Is this attributable to some bug in how notmuch handles mh folders, or does this happen with maildirs? Thanks.