Re: Gnus slow?

[Katsumi Yamaoka <yamaoka@jpl.org>]

I also tried ELP on No Gnus v0.2 and the latest CVS.  The result
is that the latest CVS is faster than No Gnus v0.2 10 to 20%.
It will be meaningless to compare it with your result since I
subscribe to two foreign servers using nntp-open-via-(ssh and
telnet), the local news server, many shimbun groups and the nnml
groups, though.

>>>>> In <87r7n0zjx9.fsf@orebokech.com> Romain Francoise wrote:

(No Gnus checkout as of May 12th)
> Package gnus, version A (first 10 lines):
> Function Name                     Call Count  Elapsed Time  Average Time
> ================================  ==========  ============  ============
> gnus-activate-group               405         0.6969249999  0.0017208024

(the latest CVS)
> Package gnus, version B (first 10 lines):
> Function Name                     Call Count  Elapsed Time  Average Time
> ================================  ==========  ============  ============
> gnus-activate-group               808         28.273399000  0.0349918304

> - version B activates twice as many groups as version A.

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

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.