Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric S Fraga <e.fraga@ucl.ac.uk>
To: ding@gnus.org
Subject: Re: is nnmaildir very slow?
Date: Sun, 19 May 2019 10:20:49 +0100	[thread overview]
Message-ID: <874l5qssum.fsf@ucl.ac.uk> (raw)
In-Reply-To: <cuca7fkrq33.fsf@gmail.com>

On Saturday, 18 May 2019 at 06:53, George Clemmer wrote:
> 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.

Yes, this agrees with my experience.  But as I do use three systems each
day, I do have to start up Emacs several times and the delay each time
is rather annoying.

I've solved the problem by expiring more (archiving) and splitting more
creatively so as to keep my inbox small.

>> I use gnus on three different systems: home, mobile device (Gemini PDA),
>> and office, using unison to synchronize all files between the three
>> systems.
>
> Cool! Would you recommend the Gemini?

Difficult to say.  I really like it but I'm waiting impatiently for the
Pyra.  The issue is that the Gemini is fragile when it comes to Debian
as it was really intended as an Android device.  I do have the Linux-fu
necessary to keep it going okay but I do have some wariness in
recommending it more generally.  The Pyra, however, will be Debian from
top to bottom so should be robust as was the OpenPandora it is replacing
(and which I used for years).

>> So maybe it's something to do with how my files are
>> synchronized.  Unison is being asked to synchronize .newsrc.eld and the
>> Maildir (& Mail & News) directories.
>
> How well does that work? Are all your Gnus marks really keep in sync? I
> would think marks would get jumbled if the systems receive mail
> independently.

That's one of the reasons for using nnmaildir: downloading emails on
different systems does not cause problems with synchronization.  I've
not had gnus get confused (yet).  But that may be why nnmaildir is so
slow on start-up.

thanks,
eric

-- 
Eric S Fraga via Emacs 27.0.50 & org 9.2.3 on Debian buster/sid




  reply	other threads:[~2019-05-19  9:20 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 [this message]
2019-05-20  9:53           ` Eric S Fraga
2019-05-24 21:26             ` Eric Abrahamsen
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=874l5qssum.fsf@ucl.ac.uk \
    --to=e.fraga@ucl.ac.uk \
    --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).