From: James Cloos <cloos@jhcloos.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: ding@gnus.org
Subject: Re: is nnmaildir very slow?
Date: Thu, 16 May 2019 13:27:48 -0400 [thread overview]
Message-ID: <m35zqae2cr.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <87v9yb6k1z.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Thu, 16 May 2019 06:32:40 +0100")
>>>>> "EF" == Eric S Fraga <e.fraga@ucl.ac.uk> writes:
EF> server. Unfortunately, however, [nnmaildir] seems to be very slow
EF> at the initial scan, taking up to several minutes within the
EF> gnus-request-scan function (I added some gnus-message lines in
EF> gnus-int.el). I haven't figured out yet why it is so slow.
I switched some years back to nnimap on a sql-backed imap daemon for
that very reason.
I don't know whether it still does, but it used to scan through the
groups three times every time I started.
Which took *horribly* long back on that laptop's ide drive and shared
ram/io bus.
On top of that bug, part of the issue is using the filesystem as a
database. Anything using that style of storage suffers a superlinear
delay as the size grows.
I'd start by watching emacs with something like strace -e open to see
whether it still loops through all of the groups multiple times.
That bug still requires a fix if so.
Otherwise a general profile of a startup probably would help.
-JimC
--
James Cloos <cloos@jhcloos.com> OpenPGP: 0x997A9F17ED7DAEA6
next prev parent reply other threads:[~2019-05-16 17:27 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
2019-05-16 17:27 ` James Cloos [this message]
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=m35zqae2cr.fsf@carbon.jhcloos.org \
--to=cloos@jhcloos.com \
--cc=ding@gnus.org \
--cc=e.fraga@ucl.ac.uk \
/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).