Performance-issues with large threads

diff --git a/da/6d948682763eac7c74e0850b3cb86a85de1e32 b/da/6d948682763eac7c74e0850b3cb86a85de1e32
new file mode 100644 (file)
index 0000000..7d89e01
--- /dev/null
+++ b/da/6d948682763eac7c74e0850b3cb86a85de1e32
@@ -0,0 +1,73 @@
+Return-Path: <alpine.art.de@gmail.com>\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 167FA431FBC\r
+       for <notmuch@notmuchmail.org>; Tue, 23 Jul 2013 02:07:38 -0700 (PDT)\r
+X-Virus-Scanned: Debian amavisd-new at olra.theworths.org\r
+X-Spam-Flag: NO\r
+X-Spam-Score: -0.799\r
+X-Spam-Level: \r
+X-Spam-Status: No, score=-0.799 tagged_above=-999 required=5\r
+       tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,\r
+       FREEMAIL_FROM=0.001, RCVD_IN_DNSWL_LOW=-0.7] 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 w+S9JS8-ARxV for <notmuch@notmuchmail.org>;\r
+       Tue, 23 Jul 2013 02:07:30 -0700 (PDT)\r
+Received: from mail-bk0-f42.google.com (mail-bk0-f42.google.com\r
+       [209.85.214.42]) (using TLSv1 with cipher RC4-SHA (128/128 bits))\r
+       (No client certificate requested)\r
+       by olra.theworths.org (Postfix) with ESMTPS id E6B2F431FB6\r
+       for <notmuch@notmuchmail.org>; Tue, 23 Jul 2013 02:07:29 -0700 (PDT)\r
+Received: by mail-bk0-f42.google.com with SMTP id jk13so2932916bkc.29\r
+       for <notmuch@notmuchmail.org>; Tue, 23 Jul 2013 02:07:28 -0700 (PDT)\r
+DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;\r
+       h=from:to:subject:date:user-agent:mime-version:message-id\r
+       :content-type:content-transfer-encoding;\r
+       bh=R7tpGR9x/bemYy4rh3YXCP8I0+XNNDMiLWiOWlwdRvs=;\r
+       b=lSC87/95kqChOv1Asak87x+Q8Vf+jh6A/vtX14DfPx1R6JbVrMwE72H17Swr3SQK1Y\r
+       XPiYR2/rjfL4aQh8J2zfF5T8K3GM6rDKzXSSV3h3lTqyGtHwoStT5iCpg/5G9SnMvWyT\r
+       I+yHvU8/E/GkjA8sqpv7uofd457nN32LZQzovjal94Rq9W4+BjH9JcY+8AaVn1tU+nqJ\r
+       GBkrNwsefdbpuJ+2khZrl9h+GnlwwllU3bVouib1woVX0tlOEY1mTpH0gNghJ9VW7sqg\r
+       nyTNg5dNYmPpP15U0fXBKEeW8WOfRy2YQ4JhAxkp4ADUUzqf6u6voYXuKIGy5G3BUz8z\r
+       Cnsg==\r
+X-Received: by 10.205.22.196 with SMTP id qx4mr4351507bkb.156.1374570448694;\r
+       Tue, 23 Jul 2013 02:07:28 -0700 (PDT)\r
+Received: from localhost (p4FD0C2D8.dip0.t-ipconnect.de. [79.208.194.216])\r
+       by mx.google.com with ESMTPSA id ok9sm7867159bkb.8.2013.07.23.02.07.27\r
+       for <notmuch@notmuchmail.org>\r
+       (version=TLSv1.2 cipher=ECDHE-RSA-RC4-SHA bits=128/128);\r
+       Tue, 23 Jul 2013 02:07:28 -0700 (PDT)\r
+From: Franz Fellner <alpine.art.de@gmail.com>\r
+To: <notmuch@notmuchmail.org>\r
+Subject: Performance-issues with large threads\r
+Date: Tue, 23 Jul 2013 11:09:15 +0200\r
+User-Agent: trojita/v0.3.93-100-gbbf4022-dirty; Qt/4.8.4; X11; Linux; \r
+MIME-Version: 1.0\r
+Message-ID: <027633b9-200d-4174-a8b5-72daff923b93@gmail.com>\r
+Content-Type: text/plain; charset=utf-8; format=flowed\r
+Content-Transfer-Encoding: quoted-printable\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, 23 Jul 2013 09:07:38 -0000\r
+\r
+Hi,=0A=0A"Large" in the context of this issue is >20 replies, I have to=\r
+ wait ~1 sec until the thread shows up. With larger conversations it ge=\r
+t's worse (a bug report on bugs.kde.org with ~400 replies takes ~13 sec=\r
+s. to load).=0AThis is due to the fact, that notmuch-{vim,emacs} load t=\r
+he complete mail including the body.=0Aner does a great job here, it lo=\r
+ads all headers but only the body of the first unread mail, resulting i=\r
+n instant loading even of gigantic conversations. It would be terrific =\r
+to see something like that, at least in my favored vim-client ;)=0A=0AT=\r
+hx=0AFranz\r