--- /dev/null
+Return-Path: <m.walters@qmul.ac.uk>\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 7C8CB431FBD\r
+ for <notmuch@notmuchmail.org>; Tue, 14 Feb 2012 04:27:30 -0800 (PST)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -1.098\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-1.098 tagged_above=-999 required=5\r
+ tests=[DKIM_ADSP_CUSTOM_MED=0.001, FREEMAIL_FROM=0.001,\r
+ NML_ADSP_CUSTOM_MED=1.2, 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 jrcJoBYri7ey for <notmuch@notmuchmail.org>;\r
+ Tue, 14 Feb 2012 04:27:30 -0800 (PST)\r
+Received: from mail2.qmul.ac.uk (mail2.qmul.ac.uk [138.37.6.6])\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 DA198431FBC\r
+ for <notmuch@notmuchmail.org>; Tue, 14 Feb 2012 04:27:29 -0800 (PST)\r
+Received: from smtp.qmul.ac.uk ([138.37.6.40])\r
+ by mail2.qmul.ac.uk with esmtp (Exim 4.71)\r
+ (envelope-from <m.walters@qmul.ac.uk>)\r
+ id 1RxHTh-0003o6-UN; Tue, 14 Feb 2012 12:27:26 +0000\r
+Received: from 94-192-233-223.zone6.bethere.co.uk ([94.192.233.223]\r
+ helo=localhost)\r
+ by smtp.qmul.ac.uk with esmtpsa (TLSv1:AES128-SHA:128) (Exim 4.69)\r
+ (envelope-from <m.walters@qmul.ac.uk>)\r
+ id 1RxHTh-0004nL-N4; Tue, 14 Feb 2012 12:27:25 +0000\r
+From: Mark Walters <markwalters1009@gmail.com>\r
+To: notmuch@notmuchmail.org\r
+Subject: Re: [RFC PATCH v3 00/11] notmuch-pick: an emacs threaded message view\r
+ with split-pane\r
+In-Reply-To: <1329096015-8078-1-git-send-email-markwalters1009@gmail.com>\r
+References: <1329072579-27340-1-git-send-email-markwalters1009@gmail.com>\r
+ <1329096015-8078-1-git-send-email-markwalters1009@gmail.com>\r
+User-Agent: Notmuch/0.11.1+203~g8b11562 (http://notmuchmail.org) Emacs/23.2.1\r
+ (i486-pc-linux-gnu)\r
+Date: Tue, 14 Feb 2012 12:28:48 +0000\r
+Message-ID: <87haytbnun.fsf@qmul.ac.uk>\r
+MIME-Version: 1.0\r
+Content-Type: text/plain; charset=us-ascii\r
+X-Sender-Host-Address: 94.192.233.223\r
+X-QM-SPAM-Info: Sender has good ham record. :)\r
+X-QM-Body-MD5: e60b2b6677e15dcdacee110fbbe5bbb5 (of first 20000 bytes)\r
+X-SpamAssassin-Score: -1.8\r
+X-SpamAssassin-SpamBar: -\r
+X-SpamAssassin-Report: The QM spam filters have analysed this message to\r
+ determine if it is\r
+ spam. We require at least 5.0 points to mark a message as spam.\r
+ This message scored -1.8 points.\r
+ Summary of the scoring: \r
+ * -2.3 RCVD_IN_DNSWL_MED RBL: Sender listed at http://www.dnswl.org/,\r
+ * medium trust\r
+ * [138.37.6.40 listed in list.dnswl.org]\r
+ * 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail\r
+ provider * (markwalters1009[at]gmail.com)\r
+ * -0.0 T_RP_MATCHES_RCVD Envelope sender domain matches handover relay\r
+ * domain\r
+ * 0.5 AWL AWL: From: address is in the auto white-list\r
+X-QM-Scan-Virus: ClamAV says the message is clean\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, 14 Feb 2012 12:27:30 -0000\r
+\r
+\r
+I have now done some benchmarking/profiling of the notmuch-pick\r
+mode. These are all done running locally (i.e., no ssh, nfs or anything)\r
+but on a fairly old computer with a slow hard disk. The timings given\r
+are for the second run (so the files and database are in cache).\r
+\r
+The profiling is done by inserting (message "%s" (current-time)) at\r
+various points.\r
+\r
+For displaying the thread structure of the whole notmuch mailing list\r
+archive (circa 10,000 messages) it takes about 18 seconds which breaks\r
+down as 6.5 seconds for the cli part, 9.5 seconds for the json parsing\r
+in emacs and 1.5 seconds for constructing the thread structure and\r
+writing the buffer in emacs.\r
+\r
+Using Austin's optimised json.el (id:"20110720205007.GB21316@mit.edu")\r
+the 9.5 seconds reduces to about 2.5 seconds (so the total reduces to\r
+about 10.5 seconds).\r
+\r
+I think the 6.5 seconds of command line time involves quite a lot of\r
+parsing of the message files (to get the headers) and this could\r
+probably be sped up by storing more of the headers in the database, or\r
+just not outputting all of them. Removing all of the calls to\r
+notmuch_message_get_header seems to reduce the 6.5s to about 1.5s\r
+\r
+In other cases, though, notmuch-pick is a noticeable speed win: namely\r
+`picking' is faster than `showing' for longer threads (as one would\r
+expect since pick only gets the thread structure and one message body\r
+whereas show gets the thread structure and all messages bodies). So for\r
+a thread of 170 messages show takes 5 seconds and pick takes less than\r
+0.5 seconds, and for a thread of 30 messages show takes 600 milliseconds\r
+and pick takes takes 150 milliseconds.\r
+\r
+Finally, if notmuch-pick were able to do work asynchronously (as\r
+notmuch-search does now) then I think all the speed concerns would go\r
+away. However, I am not sure how to do incremental json parsing.\r
+\r
+Best wishes\r
+\r
+Mark\r
+\r
+\r
projects / notmuch-archives.git / commitdiff