Subject: [sup-talk] Sup Resource Usage

From: [email-masked] (Andrei Thorp)
Date: Fri, 31 Jul 2009 11:23:07 -0400

This isn't a serious complaint, but I'd just like to bring a couple
things with respect to Sup resource usage to the light.

According to top, Sup uses a fair bit of ram: about 30 MB at any point.
For comparison, pidgin uses about that much, and firefox uses 4x more.
That's generally acceptable, but more than I'd expect from a CLI app.
This is probably unavoidable.

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. By comparison, firefox
does almost exactly the same amount of wakeups, and sup is the third
thing on my list, way above my window manager/de which does considerably
more.

I wonder what could be up here. Anyway, I'm fine with it if it's
un-investigated. Cheers.
-- 
Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com)

---

From: [email-masked] (William Morgan)
Date: Fri, 31 Jul 2009 08:43:26 -0700

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>

---

From: [email-masked] (Andrei Thorp)
Date: Fri, 31 Jul 2009 12:00:00 -0400

> 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:

This program exits right away, so I don't really know how to test it.
-- 
Andrei Thorp, Developer: Xandros Corp. (http://www.xandros.com)