Re: Gnus slow?

[Romain Francoise <romain@orebokech.com>]

Katsumi Yamaoka <yamaoka@jpl.org> writes:

> I don't know why gnus-activate-group spends so many time and
> seems to be called twice in B, but it is dominant.

It is slow because in version B, Gnus issues GROUP commands to the NNTP
server and it is synchronous so it has to wait for the answer from the
server.  To make it worse, it does it twice since groups are activated
twice.

You will find captures of the NNTP conversation between Gnus and
news.gmane.org here: <URL: http://orebokech.com/tmp/gnus/>.  Version A
issues LIST ACTIVE commands only, asynchronously.  Version B first
issues GROUP commands for each of my groups, synchronously, then issues
LIST ACTIVE commands like version A, then does GROUP commands again.  I
see two separate issues:
- why does version B send GROUP commands where version A doesn't?  They
  seem unnecessary.
- even so, why does version B send them twice?

> Some gnus-* functions are inlined in it and they cannot be
> profiled by ELP individually.  So, you need to plunge a scalpel
> into those adhesion.  To do that, replace all the
> `(inline (gnus-* ...))' forms into `(gnus-* ...)' in the
> gnus-activate-group function and recompile gnus-start.el.
> Otherwise, it may be enough to only evaluate the function
> definition of gnus-activate-group using `M-x eval-region' or
> `M-x eval-last-sexp' (`C-x C-e').

> And then, perform ELP to the `gnus' package again.

I will perform more ELP tests later today, thanks for investigating this
issue.

-- 
Romain Francoise <romain@orebokech.com> | There's no stronger wind than
it's a miracle -- http://orebokech.com/ | the one that blows down a
                                        | lonesome railroad line.