From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: A slowness in the Agent
Date: Sun, 02 May 2004 15:13:16 +0200 [thread overview]
Message-ID: <m3wu3vdlar.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <ud65o6t65.fsf@xpediantsolutions.com>
Kevin Greiner <kgreiner@xpediantsolutions.com> writes:
> Well, that compression has been in use for over a year now so I don't
> see why it would suddenly make gnus much slower. If you truely think
> that it is an issue, reverting back to No Gnus 0.1 will give you a
> version of gnus-agent-read-agentview that can be configured to turn
> the compression off. Hmmm... I wonder if that is what you had done;
> configured your gnus to disable the compression.
Hm... I don't think so. But I could be wrong. :-) What would the
variable to disable the compression be?
> What bothers me is that your seeing 9K calls to
> gnus-agent-read-agentview. That seems excessive unless you have 9K
> groups.
9K calls to `gnus-uncompress-sequence'. Only 90 calls to
`gnus-agent-read-agentview'.
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
prev parent reply other threads:[~2004-05-02 13:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-01 10:13 Lars Magne Ingebrigtsen
2004-05-01 15:52 ` Kevin Greiner
2004-05-02 13:13 ` Lars Magne Ingebrigtsen [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=m3wu3vdlar.fsf@quimbies.gnus.org \
--to=larsi@gnus.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).