From: James Tucker <jftucker-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Rainbows! list <rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org>
Subject: Re: impromptu Rainbows!/Zbatery user survey
Date: Thu, 17 Jun 2010 16:46:35 -0300 [thread overview]
Message-ID: <75572EBC-8A70-46F4-BCE3-3CDA30E20F63@gmail.com> (raw)
In-Reply-To: <20100616190835.GA20621-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
On 16 Jun 2010, at 16:08, Eric Wong wrote:
> Eric Wong <normalperson-rMlxZR9MS24@public.gmane.org> wrote:
>> Hi all,
>>
>> Since Rainbows! can be configured so many different ways, I'm
>> wondering about how (or even if :) people use it in production.
>
> One more question:
>
> * What proxies, if any, run in front? Either to distribute
> load between machines, handle failover for a dead machine, to serve
> static files, etc...
I do know of a bunch of folks using async Thin in production for relatively high concurrency levels (1-4k open connections) serving through nginx. I personally can't verify the numbers, as the boxes are behind doors to which I don't have keys. I don't know if this info is useful to you.
>> Behind the scenes, I've privately helped some folks deploy a few
>> production apps using ThreadSpawn (REE 2010.01), FiberSpawn
>> (1.9.1-p378), and EventMachine (REE 2010.01). I can't say more than
>> that due to confidentiality issues, but I suspect WEBrick would've been
>> more than adequate for those applications :)
>
> _None_ of these are proxied behind nginx. They only need a load
> balancer to distribute load between multiple machines and to handle
> failover if a box goes down.
>
> They either use haproxy or a similar, but overpriced black-box[1]. They
> either do pass-through (Layer 4, TCP-only) or only buffer (and possibly
> rewrite) HTTP headers (Layer 7). I forget which apps used which, but
> Rainbows! works great in all of those configurations.
>
> [1] not my decision to use it, of course :)
>
> --
> 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
_______________________________________________
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
prev parent reply other threads:[~2010-06-17 19:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 0:56 impromptu Rainbows!/Zbatery user survey Eric Wong
[not found] ` <20100616005653.GA29720-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2010-06-16 16:37 ` James Tucker
2010-06-16 19:08 ` Eric Wong
[not found] ` <20100616190835.GA20621-yBiyF41qdooeIZ0/mPfg9Q@public.gmane.org>
2010-06-17 19:46 ` James Tucker [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
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=75572EBC-8A70-46F4-BCE3-3CDA30E20F63@gmail.com \
--to=jftucker-re5jqeeqqe8avxtiumwx3w@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).