From: garoth@gmail.com (Andrei Thorp)
Subject: [sup-talk] Sup Resource Usage
Date: Fri, 31 Jul 2009 12:00:00 -0400 [thread overview]
Message-ID: <1249055796-sup-2690@Longbow> (raw)
In-Reply-To: <1249054758-sup-9479@masanjin.net>
Excerpts from William Morgan's message of Fri Jul 31 11:43:26 -0400 2009:
> What's the wakeup behavior of "ruby -esleep"?
Well, you can easily test this yourself with powertop, but just running
this command does not cause a lot of wakeups. (It's not in the top
causes list.)
> What's the behavior of this Ruby program:
>
> require 'rubygems'
> require 'ncurses'
>
> Ncurses.initscr
> c = Ncurses.getch
> Ncurses.endwin
>
> puts c
This program exits right away, so I don't really know how to test it.
--
Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com)
prev parent reply other threads:[~2009-07-31 16:00 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
2009-07-31 16:00 ` Andrei Thorp [this message]
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=1249055796-sup-2690@Longbow \
--to=garoth@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