From: Chris Mason <chris.mason@oracle.com>
To: Chris Mason <chris.mason@oracle.com>
Cc: sup-devel <sup-devel@rubyforge.org>
Subject: Re: [sup-devel] really high wakeup count in powertop
Date: Wed, 10 Nov 2010 09:41:30 -0500 [thread overview]
Message-ID: <1289399902-sup-201@think> (raw)
In-Reply-To: <1289349454-sup-1015@think>
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 our old
> friend mutt.
>
> I haven't done much ruby but can make my way through most things. If
> someone could point me at the polling function most likely to cause the
> wakeups I can work out a patch.
>
> I'm running git from this Monday, so pretty recent. Ruby 1.9.1
(This got dumped into the moderator approval queue, so I'm resending,
this time with more details)
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
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. I'll post to that bug.
-chris
_______________________________________________
Sup-devel mailing list
Sup-devel@rubyforge.org
http://rubyforge.org/mailman/listinfo/sup-devel
next prev parent reply other threads:[~2010-11-10 16:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-10 0:40 Chris Mason
2010-11-10 14:41 ` Chris Mason [this message]
2010-11-10 16:13 ` Gaute Hope
2010-11-10 18:35 ` William Morgan
2010-11-10 20:18 ` Chris Mason
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1289399902-sup-201@think \
--to=chris.mason@oracle.com \
--cc=sup-devel@rubyforge.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox