From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from localhost (localhost [127.0.0.1]) by arlo.cworth.org (Postfix) with ESMTP id E0DA06DE290F for ; Mon, 26 Jun 2017 15:42:34 -0700 (PDT) X-Virus-Scanned: Debian amavisd-new at cworth.org X-Spam-Flag: NO X-Spam-Score: -0.001 X-Spam-Level: X-Spam-Status: No, score=-0.001 tagged_above=-999 required=5 tests=[AWL=0.010, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01] autolearn=disabled Received: from arlo.cworth.org ([127.0.0.1]) by localhost (arlo.cworth.org [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id z3b7iH5kwrNF for ; Mon, 26 Jun 2017 15:42:33 -0700 (PDT) Received: from fethera.tethera.net (fethera.tethera.net [198.245.60.197]) by arlo.cworth.org (Postfix) with ESMTPS id CA1C26DE2904 for ; Mon, 26 Jun 2017 15:42:32 -0700 (PDT) Received: from remotemail by fethera.tethera.net with local (Exim 4.84_2) (envelope-from ) id 1dPcf9-0002jO-2U; Mon, 26 Jun 2017 18:39:19 -0400 Received: (nullmailer pid 9265 invoked by uid 1000); Mon, 26 Jun 2017 22:42:28 -0000 From: David Bremner To: Jan =?utf-8?Q?Huta=C5=99?= , notmuch@notmuchmail.org Subject: Re: sometimes it takes long to open folder In-Reply-To: <20170623093424.6siiaprt3fndo6sk@dhcp131-38.brq.redhat.com> References: <20170623093424.6siiaprt3fndo6sk@dhcp131-38.brq.redhat.com> Date: Mon, 26 Jun 2017 19:42:28 -0300 Message-ID: <87bmpa9xrf.fsf@tethera.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-BeenThere: notmuch@notmuchmail.org X-Mailman-Version: 2.1.23 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: Mon, 26 Jun 2017 22:42:35 -0000 Jan Huta=C5=99 writes: > Hello, > I'm using notmuch and mutt with virtual-mailboxes. Besides it is awesome > and very flexible, sometimes when opening some folders it takes too long > with mutt showing progress with "Reading messages..." in the bottom. It > takes few minutes for folder with 12k emails. > It would be useful to know if your notmuch new cronjob was running at this time; notmuch itself doesn't really do any background processing. The other useful thing from the notmuch point of view is if you could duplicate the slowness with the same search on the command line; that would eliminate mutt code as the problem. d