From: Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org>
To: Rainbows! list <rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org>
Cc: Damian Janowski <jano-eWlILCNyKRBBDgjK7y7TUQ@public.gmane.org>
Subject: Re: Out of band stuff?
Date: Tue, 10 Apr 2012 20:37:43 +0000 [thread overview]
Message-ID: <20120410203743.GF25426@dcvr.yhbt.net> (raw)
In-Reply-To: <CABAijKG0srUSc4VEk35yd9jj1NAz9VJMqLZ3Uh_xeiObgTmXvw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Damian Janowski <jano@dimaion.com> wrote:
> On Mon, Apr 9, 2012 at 12:05 AM, Eric Wong <normalperson@yhbt.net> wrote:
> > # @start is a Mutex and @thr is nil in the initialize method.
> >
> > @start.synchronize { @thr ||= aggregator_thread(env["rack.logger"]) }
> >
> > I avoid starting the background thread at initialization because it'll
> > die on fork (meaning I'd have to recheck it all the time, anyways).
> >
> > The overhead of Mutex#synchronize and @thr||= assignment is negligible
> > in most apps.
>
> One more question. Can you confirm that this technique doesn't work as
> expected using Rainbows/ThreadPool? I've found that Rack::Builder
> creates a new instance of each middleware on every request, so you'd
> end up spawning infinite aggregator threads.
Huh? How are you using Rack::Builder? unicorn/Rainbows! should always be
using Rack::Builder#to_app instead of regenerating the Rack stack every
single request.
I've been using Raindrops::Watcher for months now, mainly with
ThreadSpawn, but ThreadPool seems to work just fine and I can confirm
neither spawns infinite aggregator threads.
_______________________________________________
Rainbows! mailing list - rainbows-talk@rubyforge.org
http://rubyforge.org/mailman/listinfo/rainbows-talk
Do not quote signatures (like this one) or top post when replying
next prev parent reply other threads:[~2012-04-10 20:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-06 21:49 Out of band stuff? Damian Janowski
[not found] ` <CABAijKERMfjWzz9d8RxneV9eRJYLY6uSfEb9DEbhJh3jKLJ__w-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-09 3:05 ` Eric Wong
[not found] ` <20120409030552.GA24089-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2012-04-09 13:04 ` Damian Janowski
[not found] ` <CABAijKEa3Z9ZBFS-jX8wcvqjZ14sxKsPMbuESRvZOeLhRNBiCQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-10 20:16 ` Eric Wong
2012-04-10 20:24 ` Damian Janowski
[not found] ` <CABAijKG0srUSc4VEk35yd9jj1NAz9VJMqLZ3Uh_xeiObgTmXvw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2012-04-10 20:37 ` Eric Wong [this message]
[not found] ` <20120410203743.GF25426-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2012-04-11 1:20 ` Damian Janowski
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=20120410203743.GF25426@dcvr.yhbt.net \
--to=normalperson-rmlxzr9ms24@public.gmane.org \
--cc=jano-eWlILCNyKRBBDgjK7y7TUQ@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).