On Tue, Mar 18, 2008 at 9:49 AM, Thomas Mittelstaedt
<T.Mittelstaedt(a)cadenas.de> wrote:
Did another measurement, when 2 frames are open and xemacs goes into
"hog"-mode.
I really don't get what is going on here. All of your measurements
show the same thing: the time spent in the kernel is almost all idle
time, and very little time is spent in shared space, meaning the
libraries are not to blame either. Therefore, the problem must be in
the XEmacs code ... except that the profiled XEmacs code also doesn't
show the large block of CPU time. The CPU is spending a whole lot of
time doing something that is not being identified by any of your
tools. I've been racking my brains trying to imagine what the CPU
could be doing that doesn't get captured by profiling or tracing
tools. I'm stumped.
--
Jerry James
http://loganjerry.googlepages.com/
_______________________________________________
XEmacs-Beta mailing list
XEmacs-Beta(a)xemacs.org
http://calypso.tux.org/cgi-bin/mailman/listinfo/xemacs-beta