From: "Jan Hutař" <jhutar@redhat.com>
To: David Bremner <david@tethera.net>
Cc: notmuch@notmuchmail.org
Subject: Re: sometimes it takes long to open folder
Date: Tue, 4 Jul 2017 07:49:17 +0200 [thread overview]
Message-ID: <20170704054916.twyfau5ollz3afrv@dhcp131-38.brq.redhat.com> (raw)
In-Reply-To: <87bmpa9xrf.fsf@tethera.net>
On 2017-06-26 19:42 -0300, David Bremner wrote:
>Jan Hutař <jhutar@redhat.com> 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
Hello and thank you for the hints.
Finally it happened again. Looks like `notmuch new` was running around
midnight, then suspend&resume and few retchmail&procmails.
Anyway, on command line:
$ time notmuch search tag:archive >/tmp/aaa
real 0m4.840s
user 0m1.709s
sys 0m0.301s
and with this muttrc config:
virtual-mailboxes \
[...]
'ARCHIVE' 'notmuch://?query=tag:archive' \
[...]
when opening that "folder", it took about a minute. Looks like this is
problem with mutt then and I'll focus there.
Thank you,
Jan
--
Jan Hutar Systems Management QA
jhutar@redhat.com Red Hat, Inc.
prev parent reply other threads:[~2017-07-04 5:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-23 9:34 sometimes it takes long to open folder Jan Hutař
2017-06-26 22:42 ` David Bremner
2017-07-04 5:49 ` Jan Hutař [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20170704054916.twyfau5ollz3afrv@dhcp131-38.brq.redhat.com \
--to=jhutar@redhat.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).