Rainbows! Rack HTTP server user/dev discussion
 help / color / mirror / code / Atom feed
From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
Subject: possible ThreadSpawn + Ruby 1.8 issues
Date: Mon, 21 Dec 2009 14:10:02 -0800	[thread overview]
Message-ID: <20091221221002.GA12277@dcvr.yhbt.net> (raw)

Anybody else using this combination?  If you are, please let us know
if you have any problems with it or even if it's been working great.

I've heard (privately) about issues with accept() somehow blocking the
entire worker process under 1.8.  Obviously this really should not
happen, but I'm unable to reproduce it myself.

Exact details would be most helpful:

* minor version, patchlevel, distribution of Ruby 1.8

* architecture (green threads may behave differently on 32 vs 64-bit)

* outside patches applied (REE, MBARI, zero-copy context-switch, ...)

* ./configure options (--{disable,enable}-pthread, ...)

* application/gems that use threading features internally
  (includes any uses of the 'timeout' library, which Net::HTTP uses).

* Rainbows! version

Unfortunately, there are also IO.select bugs to worry about, too:

  http://www.daniel-azuma.com/blog/view/z2ysbx0e4c3it9/ruby_1_8_7_io_select_threading_bug
  http://redmine.ruby-lang.org/issues/show/1484

Even though we believe it's bad policy to workaround bugs when they're
fixable, 1.8 users (as evidenced by still using 1.8 :P) can be slow to
upgrade and we'll tolerate workarounds to make ThreadSpawn acceptable
under 1.8 since it's mainly designed with 1.8 in mind.

-- 
Eric Wong
_______________________________________________
Rainbows! mailing list - rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying


             reply	other threads:[~2009-12-21 22:10 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-12-21 22:10 Eric Wong [this message]
     [not found] ` <20091221221002.GA12277-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2009-12-22  0:54   ` [PATCH] possible MRI 1.8 thread fix to avoid blocking accept() Eric Wong
     [not found]     ` <20091222005421.GA23044-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2009-12-22 20:50       ` [PATCH 2/1] fix Ruby 1.8 detection for (possible) green thread fix Eric Wong
     [not found]         ` <20091222205008.GA11119-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2009-12-22 21:34           ` [PATCH 3/1] base: fix constant resolution under 1.8 for 1.8 bugfix Eric Wong

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

  List information: https://yhbt.net/rainbows/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20091221221002.GA12277@dcvr.yhbt.net \
    --to=normalperson-rmlxzr9ms24@public.gmane.org \
    --cc=rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://yhbt.net/rainbows.git/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).