>>>> "Adrian" == Adrian Aichner
<adrian(a)xemacs.org> writes:
Adrian> Raymond Toy <raymond.toy(a)ericsson.com> writes:
> I think I should qualify the slowness a bit. It seems that gnus
is
> slow. I have some folders in gnus with about 1000 unread entries. It
Adrian> Oh, and I feel guilty when I have 15 or 20 unread
Adrian> messages, because I keep them unread to make them serve as
Adrian> a to-do list :-)
I'm too lazy to sort them out even though I should. They're just old
messages with useful info that I want to remember. :-) When I had a
slow machine, gnus was too slow after about 500 or so messages, but I
have a faster machine now. :-)
Adrian> And you did not change gnus-version or configuration at all?
Oops. I also downloaded the 2005-03-07 sumo packages. I guess I
should try b18 with these to see how that is.
Adrian> gnus-use-byte-compile could be of interest.
Adrian> A gnus pre-release package just went out.
Adrian> You're not using that one yet, I guess?
No. I used to try to be on the bleeding edge, but I've run out of
blood.
Adrian> I mostly use show-memory-usage to let it guide me to kill a few big
Adrian> (usually buffers starting in SPC, which aren't shown) buffers when my
Adrian> XEmacs gets too big.
Adrian> Exiting and starting gnus also helps quite a bit.
>
Adrian> Are you building with the exact same
configuration you
Adrian> used for
Adrian> 21.5-b18?
>
>> Because I never remember how to configure
xemacs, I basically copy the
>> config (in config.status) from previous versions. However, I did
>> change from gcc 3.1 to gcc 3.4.3 in this build.
Adrian> Why not save the configure command line and rerun that?
"head config.status" gives the configure command I used. Useful when
experimenting with different configs, provided I remember to do the
configs in different directories.
Adrian> Unless you want to switch back gcc versions for other
Adrian> reasons, I would rather have you provide profiling output
Adrian> and configuration information.
The version doesn't really matter. I just decided to try 3.4.3 since
it was the latest around. I'm pretty sure some versions after 3.1
would produce a broken xemacs, so I stayed with 3.1, until now.
More info coming soon,
Ray