From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: 36714@debbugs.gnu.org
Subject: bug#36714: 27.0.50; Gnus nnmaildir taking long time to recursively visit sub-Maildirs
Date: Wed, 24 Jul 2019 11:18:32 -0700 [thread overview]
Message-ID: <87blxjnvnr.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <86ftn37cvz.fsf@protected.rcdrun.com>
Jean Louis <bugs@gnu.support> writes:
> * Eric Abrahamsen <eric@ericabrahamsen.net> [2019-07-22 19:40]:
[...]
>> I also don't think this threatens the integrity of the user's files: the
>> extra data is maintained in parallel, and doesn't interfere with the
>> messages themselves.
>
> I did read nnmaildir info page, and I have not found anything that
> would indicate what would Gnus do to my file system.
The first paragraph of the maildir section of the Gnus manual says:
‘nnmaildir’ also stores extra information in the ‘.nnmaildir/’ directory
within a maildir.
On the next page of the manual, there's a section on this group parameter:
‘nov-cache-size’
An integer specifying the size of the NOV memory cache. To speed
things up, ‘nnmaildir’ keeps NOV data in memory for a limited
number of articles in each group. (This is probably not
worthwhile, and will probably be removed in the future.) This
parameter’s value is noticed only the first time a group is seen
after the server is opened—i.e., when you first start Gnus,
typically. The NOV cache is never resized until the server is
closed and reopened. The default is an estimate of the number of
articles that would be displayed in the summary buffer: a count of
articles that are either marked with ‘tick’ or not marked with
‘read’, plus a little extra.
Noting both that the nov cache will probably go away at some point, and
how to control its size in the meantime.
(add-to-list 'gnus-parameters
'("^nnmaildir:"
(nov-cache-size . 2)
(expire-age . never)))
next prev parent reply other threads:[~2019-07-24 18:18 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 12:20 bug#36714: 27.0.50; Gnus nnmaildir taking long time to recursively visit sub-Maildirs Jean Louis
2019-07-18 19:00 ` Eric Abrahamsen
2019-07-18 19:43 ` Jean Louis
2019-07-18 20:03 ` Eric Abrahamsen
2019-07-18 20:48 ` Jean Louis
2019-07-19 0:27 ` Eric Abrahamsen
2019-07-19 6:15 ` Jean Louis
2019-07-19 17:23 ` Eric Abrahamsen
2019-07-19 17:31 ` Jean Louis
2019-07-19 18:49 ` Eric Abrahamsen
2019-07-22 8:44 ` Jean Louis
2019-07-22 17:40 ` Eric Abrahamsen
2019-07-23 7:30 ` Jean Louis
2019-07-24 18:18 ` Eric Abrahamsen [this message]
2019-07-24 18:25 ` Eric Abrahamsen
2019-07-22 8:34 ` Basil L. Contovounesios
2019-07-22 17:21 ` Eric Abrahamsen
2019-07-22 17:41 ` Eric Abrahamsen
2019-07-23 7:37 ` Jean Louis
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=87blxjnvnr.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=36714@debbugs.gnu.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.