Gnus development mailing list
 help / color / mirror / Atom feed
From: Kevin Greiner <kgreiner@xpediantsolutions.com>
Subject: Re: A slowness in the Agent
Date: Sat, 01 May 2004 10:52:50 -0500	[thread overview]
Message-ID: <ud65o6t65.fsf@xpediantsolutions.com> (raw)
In-Reply-To: <m3fzakwj4i.fsf@quimbies.gnus.org>

Lars Magne Ingebrigtsen <larsi@gnus.org> writes:

> I just cvs uppped a bit here, and Gnus suddenly was much slower than
> before.  After peeking around quite a bit, the most likely culprit is
> `gnus-agent-read-agentview', which now calls
> `gnus-uncompress-sequence' about 9K times for me.  Which takes a
> while.
>
> I've inlined the call, which helps a bit, but I think the fundamental
> problem might be that `gnus-agent-read-agentview' tries too hard.
> The Emacs reader is really very fast, and almost any compression one
> tries to do in Emacs Lisp is bound to be slower than just calling
> `read' on a huge whopping list.
>
> Or I may be poking around in the wrong place.

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.

For the record, I didn't add the compression to save disk space but to
improve performance.

What bothers me is that your seeing 9K calls to
gnus-agent-read-agentview.  That seems excessive unless you have 9K
groups.

Kevin



  reply	other threads:[~2004-05-01 15:52 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 [this message]
2004-05-02 13:13   ` Lars Magne Ingebrigtsen

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=ud65o6t65.fsf@xpediantsolutions.com \
    --to=kgreiner@xpediantsolutions.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).