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: X-Spam-Status: No, score=-3.1 required=3.0 tests=ALL_TRUSTED,AWL,BAYES_00 shortcircuit=no autolearn=unavailable version=3.3.2 X-Original-To: unicorn-public@bogomips.org Received: from localhost (dcvr.yhbt.net [127.0.0.1]) by dcvr.yhbt.net (Postfix) with ESMTP id 0B51C633805; Fri, 14 Nov 2014 11:03:07 +0000 (UTC) Date: Fri, 14 Nov 2014 11:03:06 +0000 From: Eric Wong To: Roberto Cordoba del Moral Cc: unicorn-public@bogomips.org Subject: Re: Issue with Unicorn: Big latency when getting a request Message-ID: <20141114110306.GA21328@dcvr.yhbt.net> References: <20141113210332.GA13597@dcvr.yhbt.net> <20141114071922.GA10410@dcvr.yhbt.net> <20141114100208.GA7416@dcvr.yhbt.net> <20141114102857.GA13910@dcvr.yhbt.net> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: List-Id: Roberto Cordoba del Moral wrote: > I´m getting this warn message when starting NGINX > > nginx: [warn] 1024 worker_connections exceed open file resource limit: 256 > Could it be related to this? Probably not. You could try "ulimit -n 1024" before starting nginx (assuming you have proper permissions). You'd have to really do something strange in your client scripts to have a browser open more than 256 connections to a single page load. I seem to remember browsers (by default) will only open 4-8 connections to a single host at once. Try increasing worker_processes in unicorn (not nginx). Or try Thin/Puma, since WEBrick works. unicorn is _not_ a good choice if you're doing any long-lived HTTP connections or any slow request processing.