From: Simon Josefsson <jas@extundo.com>
Subject: Re: Slow reading new news: explanation
Date: Thu, 24 Oct 2002 17:53:09 +0200 [thread overview]
Message-ID: <ilu1y6fhlzu.fsf@latte.josefsson.org> (raw)
In-Reply-To: <873cqwgik9.fsf@gvdnet.dk>
Martin Christensen <knightsofspamalot-factotum@gvdnet.dk> writes:
>>>>>> "Jesper" == Jesper Harder <harder@myrealbox.com> writes:
>>> Simply by hitting a wrong key in the group buffer did I
>>> accidentally put the nntp backend under Agent management --
>>> something that I thought Gnus had automatically done for me, since
>>> I'd recently upgraded from CVS, and I'd never knowingly touched any
>>> Agent settings.
> Jesper> The behaviour changed recently to turn the agent on by default
> Jesper> -- so you don't necessarily have to hit the wrong key to
> Jesper> enable the agent unknowingly. From 'GNUS-NEWS':
>
> The slowdown started not immediately after upgrading Gnus, but only
> some time after when I specifically recall hitting a wrong key or two
> (I was typing in a different frame than I thought I were). But of
> course, enabling the agent by default along with the following gold
> nugget from the changelog,
>
> 2002-08-26 Simon Josefsson <jas@extundo.com>
>
> * gnus-agent.el (gnus-agent-auto-agentize-methods): New variable.
> (gnus-agentize): Auto agentize all nntp and nnimap groups.
> (gnus-agent-possibly-save-gcc): Autoload.
> Suggested by (KOSEKI Yoshinori) <kose@meadowy.org>.
>
> isn't exactly helpful when you don't expect that kind of behaviour.
> What is the reasoning behind agentising by default? Without knowing
> anything for sure I would assume that the people using Gnus, and in
> particular the development version, would be the kind of users with
> the least need for such a feature, though of course it's attractive
> to some users.
>
> I think that a word of warning about slowdowns should be added to the
> documentation.
The point of the change was to speed up Gnus. A slowdown is not to be
expected. I think you see a bug, could you make a bug report?
Ideally including the profiling and protocol traces you mentioned in
your earlier message.
parent reply other threads:[~2002-10-24 15:53 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <873cqwgik9.fsf@gvdnet.dk>]
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=ilu1y6fhlzu.fsf@latte.josefsson.org \
--to=jas@extundo.com \
/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).