From: Ben Wing <ben@xemacs.org>
Cc: ding@gnus.org, xemacs-beta@xemacs.org
Subject: Re: Speed difference in Gnus
Date: Wed, 26 Oct 2005 20:02:37 -0500 [thread overview]
Message-ID: <4360272D.8080008@xemacs.org> (raw)
In-Reply-To: <8764rkr5cp.fsf@mat.ucm.es>
Uwe Brauer wrote:
>>>>>>"David" == David Kastrup <dak@gnu.org> writes:
>>>>>>
>>>>>>
> >>
> >>>>>>>> "David" == David Kastrup <dak@gnu.org> writes:
> >>>
> David> M-x elp-results RET
> >>>
> >>> Thanks, this function also exists in xemacs (and I did not know
> >>> about it), in any case the information is very aehm spare:
> >>
> >> You should probably also instrument the `nnml', `imap', `mm' and `mml'
> >> packages (and maybe some more depending on which operation you're
> >> benchmarking -- I don't recall).
>
>
> David> And it helps to run the test first before instrumenting it: that way
> David> not only the autoloads get instrumented.
>
>Ok, thanks, I think now more or less I know how to proceed. As I said
>before the situation is sort of strange: for a certain amount of msg,
>say n, both emacsen are almost equal, gnu emacs a little faster, once
>the number of msg > n, then xemacs got stacked.
>
>
it would be very nice to know where the problem is. sometimes typing
Control-Shift-G in XEmacs will break out and give you a backtrace. (it
should always do that but maybe sometimes doesn't ...) If not, try
setting Options->Troubleshooting->Debug on Quit, then manually do `kill
-INT ###', where ### is the process id of XEmacs. (maybe it's `kill
-SIGINT ###', i forget)
>I should add, that the information of the elp packages is detailed the
>profile-command of xemacs gives far more information. I don't know how
>important profiling is for emacs, but may that pkg could be ported?
>
>
the problem is that the XEmacs profile stuff depends on C support, which
is how it's able to do all the nifty things it does.
ben
next prev parent reply other threads:[~2005-10-27 1:02 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87r7ap899o.fsf@xemacs.org>
2005-10-13 21:17 ` Reiner Steib
[not found] ` <434EFD44.7030601@xemacs.org>
[not found] ` <877jcgub0f.fsf@xemacs.org>
[not found] ` <434F3897.3050007@xemacs.org>
[not found] ` <873bn4tptq.fsf@xemacs.org>
[not found] ` <87d5m89wuf.fsf@tleepslib.sk.tsukuba.ac.jp>
[not found] ` <87y84nyuo0.fsf@mat.ucm.es>
[not found] ` <873bmulscb.fsf@tleepslib.sk.tsukuba.ac.jp>
[not found] ` <87pspypwzv.fsf@mat.ucm.es>
[not found] ` <sluuli82.fsf@smtprelay.t-online.de>
2005-10-24 16:52 ` Uwe Brauer
2005-10-24 18:24 ` David Kastrup
2005-10-25 9:50 ` Uwe Brauer
2005-10-25 10:48 ` David Kastrup
2005-10-25 17:50 ` Jesper Harder
2005-10-25 22:07 ` David Kastrup
2005-10-26 9:32 ` Uwe Brauer
2005-10-27 1:02 ` Ben Wing [this message]
2005-10-27 9:24 ` Uwe Brauer
2005-10-28 9:52 ` Uwe Brauer
2005-10-28 11:09 ` Simon Josefsson
2005-10-28 11:55 ` Uwe Brauer
2005-10-28 12:27 ` Simon Josefsson
2005-10-28 12:06 ` Uwe Brauer
2005-10-28 12:28 ` Simon Josefsson
2005-10-28 14:05 ` Uwe Brauer
2005-10-28 14:31 ` Simon Josefsson
2005-10-28 15:53 ` Uwe Brauer
2005-10-31 7:05 ` Ben Wing
2005-10-28 10:04 ` Uwe Brauer
2005-10-24 21:00 ` Reiner Steib
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=4360272D.8080008@xemacs.org \
--to=ben@xemacs.org \
--cc=ding@gnus.org \
--cc=xemacs-beta@xemacs.org \
/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).