Two possibilities come to mind:
One is lazy lock, as you have messages like these:
Fontifying post_office.h... (regexps)...................
Fontifying post_office.h... (regexps)...................
Another is the clearcase stuff, as you've got lots of clearcase-
related itimers (I don't know how much of a performance impact these
have, but you've got a lot of them -- almost 20). You'll probably have
to ask the people who wrote the clearcase integration about this.
I'm running an old version of XEmacs (21.4.5 -- yeah, I need to
upgrade) under HP-UX 11.11i, and the idle CPU time usage is minimal
(under 0.3% or so -- it would be smaller, but I've got display-time
turned on). Overall CPU time is pretty high, but then I do just about
everything with a single XEmacs process that runs 24x7.
On a separate topic, regarding VNC: vnc/tightvnc may appear to be
"fantastically expensive" in terms of CPU time, but it really isn't that
bad. Yes, the vnc virtual screen is active "all of the time" but,
unless you've got something that's actually updating the screen, the CPU
load is minimal. I've got a vnc server, running under HP-UX 11.11i,
that's been running since August 7th (say, 48 days). Current CPU
utilization of Xvnc is around 0.2%, with a total CPU time of around 137m
40s. It would probably be less, but I've got top(1) running in a
window. Now, 137:40 is 8260 seconds; divide that by 47 days (I'm
subtracting one day since I may have started vnc late in the day, and
it's still early right now), and we have an average of 176
CPU-seconds/day. Considering that there are 86400 seconds in a day,
this is an average CPU load of just above 0.2%. In other words, VNC's
idle CPU usage is minimal. Now, if processes are constantly updating
the vnc display, especially with large areas being *rapidly* redrawn,
then the CPU usage can skyrocket.
[ Side note: while the idle CPU usage can be minimal, the memory usage
on the server is not. The (unix) vnc server runs a complete X
session, and the memory requirements of X is generally *NOT* small. ]
--
Darryl Okahata
darrylo(a)soco.agilent.com
DISCLAIMER: this message is the author's personal opinion and does not
constitute the support, opinion, or policy of Agilent Technologies, or
of the little green men that have been following him all day.