From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: is nnmaildir very slow?
Date: Fri, 24 May 2019 14:26:04 -0700 [thread overview]
Message-ID: <87a7fbee8j.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <871s0tzc3g.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Saturday, 18 May 2019 at 06:53, George Clemmer wrote:
>> Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>>
>>> On Thursday, 16 May 2019 at 14:29, Eric Abrahamsen wrote:
>>>> But after that is it quick? I can't imagine it's regenerating the NOV
>>>> files at every startup...
>>>
>>> It is quick after the initial startup. I don't know if it is slow at
>>> every startup.
>>
>> In my experience, as long as I kept Emacs running the performance was
>> great and ~ to Mu4E. The hit was only associated with an Emacs restart.
>
> I've done more experimenting. The problem is definitely at startup and
> *only* after I have synchronized systems. The maildir scan is a "deep"
> one, it seems, based on whether the directory has been modified. An
> indication of modification is taken purely from the time attribute. So,
> my synchronization makes gnus think the contents have changed.
>
> I don't know how to get around this...
I can't think of any way to get around it, except maybe by saving a
"last modified" time along with the server information in the files
you're syncing...
next prev parent reply other threads:[~2019-05-24 21:26 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-16 5:32 Eric S Fraga
2019-05-16 15:04 ` George Clemmer
2019-05-16 21:00 ` Eric S Fraga
2019-05-16 16:22 ` Eric Abrahamsen
2019-05-16 21:01 ` Eric S Fraga
2019-05-16 21:29 ` Eric Abrahamsen
2019-05-17 6:02 ` Eric S Fraga
2019-05-18 10:53 ` George Clemmer
2019-05-19 9:20 ` Eric S Fraga
2019-05-20 9:53 ` Eric S Fraga
2019-05-24 21:26 ` Eric Abrahamsen [this message]
2019-05-25 9:23 ` Eric S Fraga
2019-05-16 17:27 ` James Cloos
2019-05-16 21:02 ` Eric S Fraga
2019-05-16 21:40 ` Andreas Schwab
2019-05-17 17:46 ` James Cloos
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a7fbee8j.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.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.
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 NNTP newsgroup(s).