Hal Burgiss wrote:
> I haven't noticed a slowdown, but would like to have an idea what kind
> of load the system is under.
That's the reason I was concerned about it, too. It seems, however,
it's not important enough to spend the time to get right. I'm not too
worried. It only affects applications that use UNIX sockets, and I'm
not running any production servers with SMP _and_ X.
> The other thing I didn't mention, is that
> I flashed a new BIOS, and these spikes became constant loads. Cold
> boot into X was taking 30% CPU with 2.2.15pre7. I backed down to
> 2.2.14 and the constant load is gone, but still have the spikes.
> Curious too that some apps are not effected at all -- Netscape and
> gvim so no bump at all. Some are marginally effected -- Eterm, wmaker,
> asMixer. Strange...
It's directly proportional to the use of the UNIX socket. Applications
that update their displays frequently will appear to use a lot of
processor time, since they're writing to their UNIX socket, which is
connected to the X server.
The funny part is that the worst offenders are GNOME applets. Pretty
much all other X applications update their display when it changes, or
when it gets an X exposure event. Not GNOME applets, no sir. Take the
gnome mixer applet. Upates ever 90 milliseconds, whether it needs to or
not. As a lot, they're badly behaved; and if it weren't for them, I
probably would never have seen this oddity :)
> Also I see this, especially during the spikes:
>
> 74 processes: 71 sleeping, 3 running, 0 zombie, 0 stopped
>
> Are 3 concurrent processes possible with 2 CPUs? I didn't think so,
> and don't see how.
>
> The more I learn, the more confused I get ;)
Sure it is. I think. It should mean that three applications are
actively processing something, and not blocking. That's what
multitasking is for :)
MSG
--
To unsubscribe: mail [EMAIL PROTECTED] with "unsubscribe"
as the Subject.