unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Roberto Cordoba del Moral <roberto.chingon@hotmail.com>
To: Eric Wong <e@80x24.org>
Cc: "unicorn-public@bogomips.org" <unicorn-public@bogomips.org>
Subject: RE: Issue with Unicorn: Big latency when getting a request
Date: Fri, 14 Nov 2014 23:36:20 +0100	[thread overview]
Message-ID: <DUB126-W95ED90236B5DDBCBBFB228F88C0@phx.gbl> (raw)
In-Reply-To: <20141114183434.GA1177@dcvr.yhbt.net>

I have tested with 5 workers and still the same issue.
It´s strange, If this is happening to everyone, it should be a more known problem. I have search everywhere in Internet and I couldn´t find anything related to it.
My guess is that probably I have something in my Rails code related to sessions or cookies that is handled in a different way in the browsers but it´s also related to the application server.
I don´t know. But although I feel really curious with the isssue and I would love to find it out, I think I will try with Puma.
Thank you so much for your time.

> Date: Fri, 14 Nov 2014 18:34:34 +0000
> From: e@80x24.org
> To: roberto.chingon@hotmail.com
> CC: unicorn-public@bogomips.org
> Subject: Re: Issue with Unicorn: Big latency when getting a request
> 
> Roberto Cordoba del Moral <roberto.chingon@hotmail.com> wrote:
> > I have installed Puma and it´s working.
> > It´s the combination of Unicorn and Chrome which is not working. I
> > don´t know why.
> 
> Just curious, can you try configuring "worker_processes 4" in unicorn
> (or maybe increase 4 to 8 or any hihgher number if you have enough
> memory).  If extra workers works, it's definitely the lack of baked-in
> concurrency in unicorn (this is by design).
> 
> So I suspect puma (or any other server) is better for your use case
> anyways.
 		 	   		  

      reply	other threads:[~2014-11-14 22:36 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
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 [this message]

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=DUB126-W95ED90236B5DDBCBBFB228F88C0@phx.gbl \
    --to=roberto.chingon@hotmail.com \
    --cc=e@80x24.org \
    --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).