Archive of RubyForge sup-talk mailing list
 help / color / mirror / Atom feed
From: wmorgan-sup@masanjin.net (William Morgan)
Subject: [sup-talk] Sup Resource Usage
Date: Fri, 31 Jul 2009 08:43:26 -0700	[thread overview]
Message-ID: <1249054758-sup-9479@masanjin.net> (raw)
In-Reply-To: <1249053483-sup-9050@Longbow>

Reformatted excerpts from Andrei Thorp's message of 2009-07-31:
> What I find a bit more curious is Sup's wakeups. According to
> powertop, sup is actually one of the top power munchers on my
> computers. I don't understand why it has to wake up as often as it
> does: it's responsible for 20% of all wakeups, with a rating of ~115.

What's the wakeup behavior of "ruby -esleep"?

What's the behavior of this Ruby program:

  require 'rubygems'
  require 'ncurses'

  Ncurses.initscr
  c = Ncurses.getch
  Ncurses.endwin

  puts c

I'd also be curious if things change under Ruby 1.9.1, since I'd like to
move to that as soon as feasible.
-- 
William <wmorgan-sup at masanjin.net>


  reply	other threads:[~2009-07-31 15:43 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-31 15:23 Andrei Thorp
2009-07-31 15:43 ` William Morgan [this message]
2009-07-31 16:00   ` Andrei Thorp

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=1249054758-sup-9479@masanjin.net \
    --to=wmorgan-sup@masanjin.net \
    /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