Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Kevin Shell <kshell@gmx.com>
To: info-gnus-english@gnu.org
Subject: Re: Gnus limit: opening huge group
Date: Sat, 21 Nov 2020 10:06:51 +0800	[thread overview]
Message-ID: <20201121020651.i25hwv5bmwg6vi5v@fedora.osfans.org> (raw)
In-Reply-To: <87sg9350xw.fsf@ericabrahamsen.net>

On Fri, Nov 20, 2020 at 10:37:47AM -0800, Eric Abrahamsen wrote:
> Kevin Shell <kshell@gmx.com> writes:
>
> > Hello Gnus users.
> >
> > When I try to open very huge newsgroup with
> > C-u <Enter>
> > and request fetching all the news messages
> > Gnus behaves badly,
> > the CPU makes very loud noise and Gnus can't open the group.
> > The Gnus's fetching speed compares with neomutt is relatively slow,
> > is the probelm with Emacs lisp VS C?
> > Noemutt can open huge group with header cache,
> > but Gnus just can't open huge group.
>
> Is this an nntp server, or some other backend?
It's nntp backend.

>You mention newsgroups,
> which sounds like nntp, but also neomutt, which sounds like mail.
neomutt also supports nntp.

>Not that I'm going to have much of a solution for you, but I do feel like
> nntp handles large groups without too much trouble. Even if it takes a
> while, it shouldn't spin up your fans.
Gnus takes very long time to open,
often eventually can't open huge group.
Reguarding huge group,
Emacs lisp VS C does have some performance impact.


>If it's maildir, Gnus does
> currently have trouble with large message stores, mostly because it is
> building the header cache and that is very slow/is done inefficiently/is
> plagued by gremlins.

It's not maildir this time.
It's seems you remembered
I have asked a question about Maildir/Maildir++. :-)

>
> Someone™ will get around to fixing that eventually, but for the time
> being it is slow.
That's great!
Thank you for all the hard work improving Gnus.

--
kevin

An optimist is a guy that has never had much experience.
		-- Don Marquis

_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2020-11-21  2:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-20 13:30 Kevin Shell
2020-11-20 18:37 ` Eric Abrahamsen
2020-11-21  2:06   ` Kevin Shell [this message]
2020-11-21 21:46     ` Eric Abrahamsen
2020-11-21 22:24     ` Eric Abrahamsen
2020-11-22  3:21       ` Kevin Shell
2020-11-22 16:32         ` Eric Abrahamsen

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=20201121020651.i25hwv5bmwg6vi5v@fedora.osfans.org \
    --to=kshell@gmx.com \
    --cc=info-gnus-english@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.
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).