Top wakeups causers

[Adam Jackson]

On Mon, 2007-05-14 at 11:08 -0700, Arjan van de Ven wrote:
> Adam Jackson wrote:
> > On Mon, 2007-05-14 at 19:50 +0300, Aaron Baff wrote:
> > 
> >> Hmm...this sounds like it has something to do with either
> >> Enlightenment17 or the binary NVidia drivers I have. E17 has some
> >> nifty features which let you have a background that actually morphes
> >> (basically a mini graphics program). However when I turn it off and
> >> just use a static background the setitimer() usage does drop quite a
> >> bit so it may not be that.
> > 
> > The other thing I'm concerned about with the setitimer accounting is
> > that, afaict, it's not distinguishing between asking for a timer to
> > expire at some point in the future, and actually having that timer
> > expire and the signal delivered. 
> 
> timer_stats is only timers that actually fire. If you kill them in 
> time they won't show

That still seems implausible.  Sitting at gdm, with the cursor not
blinking, I'm seeing setitimer firing ~10 times per sample period.  I
can't imagine X is doing over 200ms worth of work over 5 seconds,
there's just nothing happening.

I'll hack something up to whinge about clients we punish for taking long
timeslices.  I suspect we're just not clearing the timer as much as we
should.

- ajax