Gnus development mailing list
 help / color / mirror / Atom feed
From: Erik Colson <eco@ecocode.net>
To: ding@gnus.org
Subject: Re: maildir and gnus
Date: Wed, 04 May 2022 14:31:54 +0200	[thread overview]
Message-ID: <87v8ul32dh.fsf@ecocode.net> (raw)
In-Reply-To: <87h773lnui.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Fri, 08 Apr 2022 14:13:41 +0100")

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> On Friday,  8 Apr 2022 at 14:34, Erik Colson wrote:
>> Some years ago I used Gnus extensively but eventually moved to mu4e for
>> speed reasons.
>> Today I'm reconsidering Gnus.  What is the recommended setup for mbsync
>> with local maildir usage?  Is speed still an issue?
>
> Hi Erik,
>
> speed can be an issue with nnmaildir.  It depends on what mbsync does to
> file update times in the various maildir directories.  I switched to
> nnml for my local email storage as it's a lot more efficient.  For
> nnmaildir, my groups had to be rescanned every time and this operation
> takes O(n^4) time, where n is the number of emails in the group.  The
> rescanning was necessary, in my case, because I was using unison to keep
> 3-4 systems in sync which meant that gnus had to regenerate the index
> tables it uses for each group.
>
> But if mbsync is smart, you may not encounter this issue.  Try it and
> see?

So I finally installed the thing: mbsync / dovecot / nnimap

Still some issues but not speed actually.

best
-- 
erik colson


  reply	other threads:[~2022-05-04 12:32 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-08 12:34 Erik Colson
2022-04-08 13:13 ` Eric S Fraga
2022-05-04 12:31   ` Erik Colson [this message]
2022-05-25 18:20     ` Wes Hardaker

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=87v8ul32dh.fsf@ecocode.net \
    --to=eco@ecocode.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).