From: garoth@gmail.com (Andrei Thorp)
Subject: [sup-talk] Sup Resource Usage
Date: Fri, 31 Jul 2009 11:23:07 -0400 [thread overview]
Message-ID: <1249053483-sup-9050@Longbow> (raw)
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)
next reply other threads:[~2009-07-31 15:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-31 15:23 Andrei Thorp [this message]
2009-07-31 15:43 ` William Morgan
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=1249053483-sup-9050@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