unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: Troex Nevelin <list@mrtech.ru>
To: mongrel-unicorn@rubyforge.org
Subject: Re: Request queue length
Date: Sat, 12 Feb 2011 18:58:35 +0300	[thread overview]
Message-ID: <4D56AE2B.1040107@mrtech.ru> (raw)
In-Reply-To: <20110211212036.GA26634@dcvr.yhbt.net>

On 02/12/2011 12:20 AM, Eric Wong wrote:
> Thin can hold multiple connections open in a single process (idle or
> doing I/O), but only execute the Rack app for one client at a time
> (unless you're using the non-standard "app.deferred?" stuff).

No I'm using any deferred stuff, I have delayed_job but this is other story.

> With Unicorn, you'll still see multiple active because all the worker
> processes share the same listener socket, but the active numbers
> will be smaller and capped at the number of worker processes you have.
> The queue is likely to be smaller if you're running multiple workers,
> too.

Currently I use thin 10 instances and pass 10 sockets to nginx. I forgot 
that unicorn uses only one socket to communicate with frontend :)
What I really want to track with unicorn is to see how many clients are 
really waiting in queue. I hope if I ran 10 unicorn instances and 
monitor socket during peak load I'll see 10 active and the queue will be 
the real queue :)
As you showed me above that thin can take requests 'on hold' and that is 
why I didn't understand the active number bigger than 1 with thin.

I'll post the results here, when I migrate to unicorn.
Unicorn mailing list - mongrel-unicorn@rubyforge.org
Do not quote signatures (like this one) or top post when replying

  reply	other threads:[~2011-02-12 16:13 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-06 14:03 Request queue length Troex Nevelin
2011-02-06 19:02 ` Eric Wong
2011-02-11 19:52   ` Troex Nevelin
2011-02-11 21:20     ` Eric Wong
2011-02-12 15:58       ` Troex Nevelin [this message]
2011-02-26 13:12         ` Troex Nevelin
2011-02-26 20:40           ` Eric Wong

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:

  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=4D56AE2B.1040107@mrtech.ru \
    --to=list@mrtech.ru \
    --cc=mongrel-unicorn@rubyforge.org \


* 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


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).