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.2 required=5.0 tests=AWL shortcircuit=no autolearn=unavailable version=3.3.2 X-Original-To: archivist@yhbt.net Delivered-To: archivist@dcvr.yhbt.net Received: from rubyforge.org (50-56-192-79.static.cloud-ips.com [50.56.192.79]) by dcvr.yhbt.net (Postfix) with ESMTP id 9FB281F736 for ; Tue, 15 Jan 2013 19:44:16 +0000 (UTC) Received: from localhost.localdomain (localhost [127.0.0.1]) by rubyforge.org (Postfix) with ESMTP id 72F562E097; Tue, 15 Jan 2013 19:44:16 +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 3C73E2E069 for ; Tue, 15 Jan 2013 19:44:11 +0000 (UTC) Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 037BB1F6C0; Tue, 15 Jan 2013 19:44:08 +0000 (UTC) Date: Tue, 15 Jan 2013 19:44:08 +0000 From: Eric Wong To: unicorn list Subject: Re: Increassing timeouts Message-ID: <20130115194408.GA30869@dcvr.yhbt.net> References: 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 Manuel Palenciano Guerrero wrote: > Hello there > > We use Unicorn in all of our production/staging web-apps, and we are > very happy with it. But we also have one of the apps talking to a > web-service via SOAP, and this web-service now takes longer than usual > processing requests. To solve this situation we have increased the > time-outs for unicorn and nginx (proxy_read_timeout and > proxy_connect_timeout) from 30 to 120, and everything works fine this > way (although I don't like it). > > My question is: having increased the time-out to 120 means this app is > now considered slow (or sleepy) and should be run by Rainbow ? or is > 120 still ok for Unicorn ? As usual, it depends. If clients hitting other endpoints are able to access your site, you're fine... But seriously, who will wait 120s for a website to load? _______________________________________________ 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