From: philsnow@gmail.com (Phil Snowberger)
Subject: [sup-talk] ruby/sup causing lots of wakeups-from-idle
Date: Sun, 11 Nov 2007 19:49:55 -0500 [thread overview]
Message-ID: <6ab4c98f0711111649o3e06c24aq73750c99bc4af248@mail.gmail.com> (raw)
I was wondering if anybody else has a problem with sup/ruby causing
lots of wakeups-from-idle? The following line comes from the output
of powertop on my thinkpad:
...
20.6% ( 94.8) ruby : do_nanosleep (hrtimer_wakeup)
...
That is, there are ~94.8 wakeups-from-idle per second occuring because
ruby is do_nanosleep'ing a lot. Is there any workaround for this?
Cursory searching seems to indicate that lots of wakeups can be caused
by doing usleep()s instead of select()/poll(). I'm trying to save as
much battery power as possible, and I currently leave sup off until I
want to check my email, which introduces startup time, etc.
I could just run it on some other host and access it with ssh, but for
a few reasons (mostly not wanting to do X forwarding), I'd like to try
getting ruby/sup to behave a little better.
Thanks,
--Phil
next reply other threads:[~2007-11-12 0:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 0:49 Phil Snowberger [this message]
2007-11-12 1:24 ` William Morgan
2007-11-13 20:26 ` Phil Snowberger
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=6ab4c98f0711111649o3e06c24aq73750c99bc4af248@mail.gmail.com \
--to=philsnow@gmail.com \
/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