Gnus development mailing list
 help / color / mirror / Atom feed
From: James Cloos <cloos@jhcloos.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: Eric S Fraga <e.fraga@ucl.ac.uk>,  ding@gnus.org
Subject: Re: is nnmaildir very slow?
Date: Fri, 17 May 2019 13:46:25 -0400	[thread overview]
Message-ID: <m3sgtdc6tq.fsf@carbon.jhcloos.org> (raw)
In-Reply-To: <87bm02qdrm.fsf@igel.home> (Andreas Schwab's message of "Thu, 16 May 2019 23:40:29 +0200")

>>>>> "AS" == Andreas Schwab <schwab@linux-m68k.org> writes:

AS> On Mai 16 2019, James Cloos <cloos@jhcloos.com> wrote:
>> 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.

AS> Not necessarily.  Modern file systems have sublinear directory lookups.

That is not the only issue.

Cache presure is often a huge issue.

nnmaildir triggered emacs' gc much more often.

Of course with ssds and 32g ram my current workstation is vastly better.

But gnus is still *slow* running gnus-group-get-new-news.


-JimC
-- 
James Cloos <cloos@jhcloos.com>         OpenPGP: 0x997A9F17ED7DAEA6



      reply	other threads:[~2019-05-17 17:46 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
2019-05-16 21:02   ` Eric S Fraga
2019-05-16 21:40   ` Andreas Schwab
2019-05-17 17:46     ` James Cloos [this message]

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=m3sgtdc6tq.fsf@carbon.jhcloos.org \
    --to=cloos@jhcloos.com \
    --cc=ding@gnus.org \
    --cc=e.fraga@ucl.ac.uk \
    --cc=schwab@linux-m68k.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).