From: Jorge Godoy <godoy@ieee.org>
Subject: Re: Gnus is very slow in displaying headers.
Date: Mon, 23 Aug 2004 09:12:57 -0300 [thread overview]
Message-ID: <m38yc6uk6u.fsf@g2ctech.com> (raw)
In-Reply-To: <4knii01atsa54v7dm0gs6taep3v1uoglj7@4ax.com>
Daniel M. <xt@nm.ru> writes:
> I noticed that even when I enter a group with a relatively small
> amount of headers - in my case, 12000 for comp.lang.lisp, it takes
> Gnus a very long time to thread/load them (headers are already in
> the spool - they were downloaded previously by the Gnus) - 3 minutes
> and 100% CPU for the duration of that period.
It doesn't happen here, but I have an nntp server (leafnode) on my LAN.
Access here is almost instantaneous, except when I happen to get an
article in HTML or some not-found-on-keyservers PGP key use to sign
messages.
> Am I doing something wrong, or is it a fundamental issue (elisp is too
> slow? something in the core of X/Emacs?) which renders Gnus unusable
> for anything more then a very small groups?
I dunno what you're doing or how, but here the reality is different. It
looks more like your Forte Agent.
> BTW, listing of all active groups (zombie, killed groups - I am not
> sure how I am supposed to call them. In effect, it is the list of all
> groups carried by the server) also takes a lot of time - almost a full
> minute, although there are only ~32000 groups and the file containing
> them resides on the HD. I even tried to sort that file, but it didn't
> help :(.
Weird.
It seems you're not using the local file, then... It is faster here and
the amount of groups is also big (Usenet + a brazilian network with a
few thousand groups).
Have you tried removing your configuration and redoing it?
Be seeing you,
--
Godoy. <godoy@ieee.org>
next prev parent reply other threads:[~2004-08-23 12:12 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-23 3:40 Daniel M.
2004-08-23 12:12 ` Jorge Godoy [this message]
2004-08-24 6:02 ` Daniel M.
2004-08-23 20:22 ` Jorge Godoy
2004-08-24 4:49 ` Kevin Greiner
2004-08-24 17:30 ` Daniel M.
2004-08-24 9:31 ` Kai Grossjohann
2004-08-24 19:44 ` Daniel M.
2004-08-24 12:05 ` Kai Grossjohann
2004-08-24 13:35 ` Derrell.Lipman
2004-08-25 6:08 ` Daniel M.
2004-08-25 7:14 ` Kai Grossjohann
2004-08-25 6:26 ` Daniel M.
2004-08-24 20:54 ` Andrew A. Raines
2004-08-25 8:57 ` Kai Grossjohann
2004-08-24 20:07 ` Jesper Harder
2004-08-25 6:34 ` Daniel M.
2004-08-26 14:50 ` ignotus
2004-08-27 23:24 ` Daniel M.
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=m38yc6uk6u.fsf@g2ctech.com \
--to=godoy@ieee.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).