[sup-devel] really high wakeup count in powertop

2010-11-10 Thread Chris Mason
Hi everyone, I'm new to sup and really like the interface and the features. But, I popped up powertop while it was running and sup accounts for a constant 100 wakeups/second, much more than the one or two wakeups/sec from our old friend mutt. I haven't done much ruby but can make my way through

Re: [sup-devel] really high wakeup count in powertop

2010-11-10 Thread Chris Mason
Excerpts from Chris Mason's message of 2010-11-09 19:40:58 -0500: > Hi everyone, > > I'm new to sup and really like the interface and the features. But, I > popped up powertop while it was running and sup accounts for a constant 100 > wakeups/second, much more than the one or two wakeups/sec from

Re: [sup-devel] really high wakeup count in powertop

2010-11-10 Thread Gaute Hope
Excerpts from Chris Mason's message of 2010-11-10 15:41:30 +0100: > strace showed we were hammering on futexes, and a little digging made it > clear sup isn't to blame. The ruby timer thread is polling for > signals (or something) every 10ms: > > http://redmine.ruby-lang.org/issues/show/3436 > >

Re: [sup-devel] really high wakeup count in powertop

2010-11-10 Thread William Morgan
Reformatted excerpts from Chris Mason's message of 2010-11-10: > I patched up ruby to poll every 500ms and things seem to work. Not > sure why the ruby developers didn't just change the timeout, but > chances are good they have a real reason. Yeah, the last time someone investigated this, they de

Re: [sup-devel] really high wakeup count in powertop

2010-11-10 Thread Chris Mason
Excerpts from William Morgan's message of 2010-11-10 13:35:41 -0500: > Reformatted excerpts from Chris Mason's message of 2010-11-10: > > I patched up ruby to poll every 500ms and things seem to work. Not > > sure why the ruby developers didn't just change the timeout, but > > chances are good the