From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on dcvr.yhbt.net X-Spam-Level: * X-Spam-ASN: AS33070 50.56.128.0/17 X-Spam-Status: No, score=1.7 required=3.0 tests=AWL,HK_RANDOM_FROM, MSGID_FROM_MTA_HEADER,RDNS_NONE shortcircuit=no autolearn=no version=3.3.2 Path: news.gmane.org!not-for-mail From: Eric Wong Newsgroups: gmane.comp.lang.ruby.rainbows.general Subject: Re: EventMachine with thread pool and thread spawn Date: Fri, 6 Sep 2013 06:52:22 +0000 Message-ID: <20130906065222.GA2727@dcvr.yhbt.net> References: <20130823225114.GA5691@dcvr.yhbt.net> <20130825215701.GA31966@dcvr.yhbt.net> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit X-Trace: ger.gmane.org 1378450348 1278 80.91.229.3 (6 Sep 2013 06:52:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 6 Sep 2013 06:52:28 +0000 (UTC) To: Rainbows! list Original-X-From: rainbows-talk-bounces-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org Fri Sep 06 08:52:32 2013 Return-path: Envelope-to: gclrrg-rainbows-talk@m.gmane.org X-Original-To: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org Delivered-To: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: rainbows-talk-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: rainbows-talk-bounces-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org Errors-To: rainbows-talk-bounces-GrnCvJ7WPxnNLxjTenLetw@public.gmane.org X-Broken-Reverse-DNS: no host name found for IP address 50.56.192.79 Xref: news.gmane.org gmane.comp.lang.ruby.rainbows.general:535 Archived-At: Received: from [50.56.192.79] (helo=rubyforge.org) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1VHpu8-0002v6-N7 for gclrrg-rainbows-talk@m.gmane.org; Fri, 06 Sep 2013 08:52:28 +0200 Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id BBDE82E185; Fri, 6 Sep 2013 06:52:27 +0000 (UTC) Received: from dcvr.yhbt.net (dcvr.yhbt.net [64.71.152.64]) by rubyforge.org (Postfix) with ESMTP id 22F402E183 for ; Fri, 6 Sep 2013 06:52:23 +0000 (UTC) Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 8BC961F5B6; Fri, 6 Sep 2013 06:52:22 +0000 (UTC) "Lin Jen-Shin (godfat)" wrote: > On Mon, Aug 26, 2013 at 5:57 AM, Eric Wong wrote: > > Anyways, it's still infuriating to me that Heroku cannot do full > > buffering and still claims to "support" unicorn. > > They do provide a way to customize the deployment, so that we could > build an Nginx while deploying and run it for each unicorn process though. > They do not officially support this, but it could work... things might break > easily if they changed something though. > > The reason why they don't fully buffer is because of latency concern > as far as I know. But I feel in most of the web apps, we don't really do > realtime stuffs. (part 2, sorry got distracted during my first reply) Latency for slow streaming? Sure, but unicorn is completely wrong for slow streaming in any direction. For fast requests/responses, any latency introduced by nginx is dwarfed by network latency to the client. > And the most frustrating thing to me is that my co-workers don't really > trust me. They still prefer unicorn because Heroku recommends it > officially even when I showed benchmarks and some people at Heroku > did admit it could be an issue. Heh, I don't get it, either. Especially given _my_ disapproval of the default Heroku setup with unicorn. Oh well, I get the feeling some unicorn users only use it because of buzz from a handful of blogs, not because they read the documentation and understand it. That probably goes for most tech :< _______________________________________________ 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