Re: [Ok, with patch] XEmacs 21.5-b20 "cilantro" (+CVS-20050310) s parc-sun-solaris2.8
Raymond Toy <raymond.toy(a)ericsson.com> writes:
>>>>> "Adrian" == Adrian Aichner
<adrian(a)xemacs.org> writes:
Adrian> Raymond Toy <raymond.toy(a)ericsson.com> writes:
>> Built from a full tarball, but I grabbed a patch to make
>> src/syssignal.h be the same as the CVS version.
>>
>> Everything seems to be ok, but it seems a quite a bit slower and more
>> consy than 21.5-b18. No hard numbers though.
Adrian> Hi Ray!
Hello!
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
Oh, and I feel guilty when I have 15 or 20 unread messages, because I
keep them unread to make them serve as a to-do list :-)
And you did not change gnus-version or configuration at all?
gnus-use-byte-compile could be of interest.
A gnus pre-release package just went out.
You're not using that one yet, I guess?
seems b20 takes a lot longer and gc's quite a bit when getting
the
summary buffer.
Providing profiling output for 21.5-b18 and 21.5-b20 might be useful.
Just use
M-x profile-command
or
M-x profile-key-sequence
whichever is more convenience for your usage pattern.
Might want to include output of (describe-installation) verbatim into
that report.
That should make it easy to use ediff-regions-wordwise or somesuch
between the two reports.
Otherwise, I haven't noticed slowness anywhere else, but I don't think
my normal usage requires lots of heavy stuff to run, except gnus.
Adrian> M-x show-memory-usage
Adrian> can easily get you the data, see the bottom section of its output.
Adrian> Make sure not to disable debugging support, which also defines
Adrian> MEMORY_USAGE_STATS.
I never turn off any debugging stuff on the betas. I'll send the
numbers and stuff later.
Great.
I mostly use show-memory-usage to let it guide me to kill a few big
(usually buffers starting in SPC, which aren't shown) buffers when my
XEmacs gets too big.
Exiting and starting gnus also helps quite a bit.
Adrian> Are you building with the exact same configuration you 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.
Why not save the configure command line and rerun that?
Is it too late for that now?
My build XEmacs Package features build-settings[1] since a little while,
which may help.
Would it matter if I changed back to 3.1? Would you be interested in
the results?
I wouldn't personally use that data.
Others might.
Unless you want to switch back gcc versions for other reasons, I would
rather have you provide profiling output and configuration
information.
Narrowing in on the fat rabbit would help.
Best regards,
Adrian
Thanks,
Ray
Footnotes:
[1] http://www.xemacs.org/Documentation/packages/html/build_4.html#SEC6
--
Adrian Aichner
mailto:adrianï¼ xemacs.org
http://www.xemacs.org/