From: philsnow@gmail.com (Phil Snowberger)
Subject: [sup-talk] ruby/sup causing lots of wakeups-from-idle
Date: Tue, 13 Nov 2007 15:26:26 -0500 [thread overview]
Message-ID: <6ab4c98f0711131226q4772e60fuda2d98fe3d3e5b7d@mail.gmail.com> (raw)
In-Reply-To: <1194830575-sup-5874@south>
On Nov 11, 2007 8:24 PM, William Morgan <wmorgan-sup at masanjin.net> wrote:
> Excerpts from Phil Snowberger's message of Sun Nov 11 16:49:55 -0800 2007:
> > I was wondering if anybody else has a problem with sup/ruby causing
> > lots of wakeups-from-idle?
>
> Does this happen with other multithreaded Ruby apps? Sup uses select()
> for input, and the only persistent threads have multi-second sleep
> times. But I have no idea how that translates down to the OS level, as
> Ruby does its own threading.
I tried raggle to see if it would cause a similar amount of wakeups,
and it does; Once it settles into a steady state (after it's checked
each feed on startup), it does ~95 wakeups per second, just like sup.
Sorry for what appears to be a false alarm; I'll take this question to
some ruby folks.
Thanks,
--Phil
prev parent reply other threads:[~2007-11-13 20:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-12 0:49 Phil Snowberger
2007-11-12 1:24 ` William Morgan
2007-11-13 20:26 ` Phil Snowberger [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=6ab4c98f0711131226q4772e60fuda2d98fe3d3e5b7d@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