From: om@iki.fi (Otto J. Makela)
To: info-gnus-english@gnu.org
Subject: Re: Gnus horribly slow after upgrade to Fedora17
Date: Thu, 01 Aug 2013 19:44:01 +0300 [thread overview]
Message-ID: <m3siyt2wfi.fsf@tigger.otto.net> (raw)
In-Reply-To: <mailman.2299.1375361875.12400.info-gnus-english@gnu.org>
Lars Magne Ingebrigtsen <larsi@gnus.org> wrote:
> "Otto J. Makela" <om@iki.fi> writes:
>> For reasons that are beyond me, the Gnus that came with Fedora17
>> (version Gnus/5.13 Emacs/24.1) is terribly slow compared to the earlier
>> one I used with Fedora16 (Gnus/5.13 Emacs/23.3). The "g" command
>> (gnus-group-get-new-news) "nntp read" takes around 20× more time.
>
> Is there a lot of data in the " *server foo... *" buffers after you hit
> `g'? (Note leading space in the buffer name.)
26881 lines in the buffer " *server news.saunalahti.fi nntp *nntpd**"
which matches what I have in my .newsrc -- when I go into a group it
seems to drop to one line.
This slow-down initially started way back when I upgraded from Fedora
16 to Fedora 17. Initially when gnus tried to open the nntp connection,
it just gave the error message:
nntp (news.saunalahti.fi) open error: 'Error when connecting: 200 Elisa
USENET News Server (Typhoon v2.2.2.503)^M'. Continue? (y or n)
I got it working by setting the following per a hint I got from the net:
(setq gnus-select-method
'(nntp "news.saunalahti.fi"
(nntp-open-connection-function network-only)
))
But ever since the upgrade I've been plagued by slowness.
What can I do to debug where the time is spent?
--
/* * * Otto J. Makela <om@iki.fi> * * * * * * * * * */
/* Phone: +358 40 765 5772, ICBM: N 60 10' E 24 55' */
/* Mail: Mechelininkatu 26 B 27, FI-00100 Helsinki */
/* * * Computers Rule 01001111 01001011 * * * * * * */
next prev parent reply other threads:[~2013-08-01 16:44 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.23482.1365059278.855.info-gnus-english@gnu.org>
2013-08-01 12:57 ` Lars Magne Ingebrigtsen
[not found] ` <mailman.2299.1375361875.12400.info-gnus-english@gnu.org>
2013-08-01 16:44 ` Otto J. Makela [this message]
2013-08-01 16:47 ` Lars Magne Ingebrigtsen
2013-08-01 17:10 ` Otto J. Makela
2013-08-01 20:56 ` Lars Magne Ingebrigtsen
2013-08-02 7:18 ` Otto J. Makela
2013-08-02 8:46 ` Anssi Saari
2013-08-02 12:30 ` Lars Magne Ingebrigtsen
2013-08-03 9:17 ` Otto J. Makela
2013-08-03 11:20 ` Lars Magne Ingebrigtsen
2013-08-05 6:18 ` Otto J. Makela
2013-08-05 7:59 ` Otto J. Makela
2013-04-03 11:30 Otto J. Makela
-- strict thread matches above, loose matches on Subject: below --
2013-01-18 7:25 Otto J. Makela
2013-02-13 13:13 ` Otto J. Makela
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=m3siyt2wfi.fsf@tigger.otto.net \
--to=om@iki.fi \
--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).