Hi Eric, the research has given an unexpected turn. I have confirmed the issue is only happening with Google Chrome. With Safari never happens. It has to be something related to cookies or cache with Chrome.
> Date: Fri, 14 Nov 2014 11:03:06 +0000 > From: [email protected] > To: [email protected] > CC: [email protected] > Subject: Re: Issue with Unicorn: Big latency when getting a request > > Roberto Cordoba del Moral <[email protected]> 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.
