From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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=0.5 required=5.0 tests=AWL,RDNS_NONE shortcircuit=no autolearn=no version=3.3.2 X-Original-To: archivist@yhbt.net Delivered-To: archivist@dcvr.yhbt.net Received: from rubyforge.org (unknown [50.56.192.79]) by dcvr.yhbt.net (Postfix) with ESMTP id 448BD1F523 for ; Thu, 22 Aug 2013 17:05:10 +0000 (UTC) Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 95A022E1E8; Thu, 22 Aug 2013 17:05:10 +0000 (UTC) X-Original-To: mongrel-unicorn@rubyforge.org Delivered-To: mongrel-unicorn@rubyforge.org Received: from dcvr.yhbt.net (dcvr.yhbt.net [64.71.152.64]) by rubyforge.org (Postfix) with ESMTP id 183F72E1D8 for ; Thu, 22 Aug 2013 17:04:53 +0000 (UTC) Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 0EB1A1F464; Thu, 22 Aug 2013 17:04:51 +0000 (UTC) Date: Thu, 22 Aug 2013 17:04:50 +0000 From: Eric Wong To: unicorn list Subject: Re: HTTP streaming and Unicorn timeout Message-ID: <20130822170450.GA6927@dcvr.yhbt.net> References: <20130821164144.GA19563@dcvr.yhbt.net> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: mongrel-unicorn@rubyforge.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: mongrel-unicorn-bounces@rubyforge.org Errors-To: mongrel-unicorn-bounces@rubyforge.org Nokan Emiro wrote: > Thank you for your answer Eric. > > > Using Rack::Timeout with Rainbows! instead of unicorn is probably a > > better idea. > > 99% of the requests are fast and can be served far below 300 ms. Only > a few type of requests need to stream lots of data. Do you really think that > unicorn isn't a good choice in this case and I should consider switching to > something else (Rack::Timeout + Rainbows!, Puma or whatever) just for the > sake of that 1%? What Hongli said. unicorn is only for sending fast responses. You'll run into scalability problems very quickly if unicorn is used for any slow response. _______________________________________________ Unicorn mailing list - mongrel-unicorn@rubyforge.org http://rubyforge.org/mailman/listinfo/mongrel-unicorn Do not quote signatures (like this one) or top post when replying