From: Eric Wong <e@80x24.org>
To: Roberto Cordoba del Moral <roberto.chingon@hotmail.com>
Cc: unicorn-public@bogomips.org
Subject: Re: Issue with Unicorn: Big latency when getting a request
Date: Fri, 14 Nov 2014 11:03:06 +0000 [thread overview]
Message-ID: <20141114110306.GA21328@dcvr.yhbt.net> (raw)
In-Reply-To: <DUB126-W58ADB3EED5FCA9D2EE0D36F88C0@phx.gbl>
Roberto Cordoba del Moral <roberto.chingon@hotmail.com> 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.
next prev parent reply other threads:[~2014-11-14 11:03 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-12 19:46 Issue with Unicorn: Big latency when getting a request Roberto Cordoba del Moral
2014-11-13 7:12 ` Roberto Cordoba del Moral
2014-11-13 21:03 ` Eric Wong
2014-11-14 6:46 ` Roberto Cordoba del Moral
2014-11-14 7:19 ` Eric Wong
2014-11-14 9:09 ` Roberto Cordoba del Moral
2014-11-14 9:32 ` Roberto Cordoba del Moral
2014-11-14 10:02 ` Eric Wong
2014-11-14 10:12 ` Roberto Cordoba del Moral
2014-11-14 10:15 ` Roberto Cordoba del Moral
2014-11-14 10:28 ` Eric Wong
2014-11-14 10:51 ` Roberto Cordoba del Moral
2014-11-14 11:03 ` Eric Wong [this message]
2014-11-14 11:15 ` Roberto Cordoba del Moral
2014-11-14 15:01 ` Roberto Cordoba del Moral
2014-11-14 18:34 ` Eric Wong
2014-11-14 22:36 ` Roberto Cordoba del Moral
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/unicorn/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20141114110306.GA21328@dcvr.yhbt.net \
--to=e@80x24.org \
--cc=roberto.chingon@hotmail.com \
--cc=unicorn-public@bogomips.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/unicorn.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).