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: Sat, 25 May 2019 10:23:11 +0100	[thread overview]
Message-ID: <875zpysxa8.fsf@ucl.ac.uk> (raw)
In-Reply-To: <87a7fbee8j.fsf@ericabrahamsen.net>

On Friday, 24 May 2019 at 14:26, Eric Abrahamsen wrote:
> 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...

So it turns out that unison has a -times option that will update the
modification time when synchronizing [1].  This should have done the job
but it didn't.  There's something being checked by gnus (in
nnmaildir--scan) that I cannot quite catch.

I've given up and moved back to nnml.  The problem with nnml is the lack
of robustness when working on multiple systems.  Just have to be more
careful...

Thanks all for suggestions etc.

Footnotes:

[1] took well over an hour to do the initial re-synchronization given
    that my synchronized file hierarchy contains 220k files... gulp.

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




  reply	other threads:[~2019-05-25  9:23 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
2019-05-25  9:23               ` Eric S Fraga [this message]
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=875zpysxa8.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).