unicorn Ruby/Rack server user+dev discussion/patches/pulls/bugs/help
 help / color / mirror / code / Atom feed
From: "Alexander Dymo" <adymo@pluron.com>
To: "unicorn list" <mongrel-unicorn@rubyforge.org>
Subject: Re: Unicorn freezes, requests got stuck in the queue most likely
Date: Tue, 28 May 2013 21:13:44 +0300	[thread overview]
Message-ID: <op.wxs3k6kjaya692@earth.site> (raw)
In-Reply-To: <20130528172036.GA9401@dcvr.yhbt.net>

> How are you determining requests get stuck for up to 7 seconds?
By measuring time between nginx gets the request and worker starts processing it.

> How is the system (CPU/RAM/swap usage) around this time?
No load at all. 14G free ram, no swap usage.

> Are you using Raindrops::LastDataRecv or Raindrops::Watcher?
> (If not and you're on Linux, please give them a try[1]).
Not yet. I'll take a look.

> Anything in the stderr logs?  Dying/restarted workers might cause this.
We are logging worker restarts, so no, no restarts/dying workers.

> I certainly have not.  Did you perform any other upgrades around this point?
Yes, we upgraded other ruby gems as well.

> Can you try reverting to 4.3.1 (or earlier, and not changing anything else)
> and see if the problem presents itself there?
Thanks, will do.

> Also, which OS/version is this?
Debian 6.0
_______________________________________________
Unicorn mailing list - mongrel-unicorn@rubyforge.org
http://rubyforge.org/mailman/listinfo/mongrel-unicorn
Do not quote signatures (like this one) or top post when replying

  reply	other threads:[~2013-05-28 18:21 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-05-28 11:17 Unicorn freezes, requests got stuck in the queue most likely Alexander Dymo
2013-05-28 17:20 ` Eric Wong
2013-05-28 18:13   ` Alexander Dymo [this message]
2013-05-30  0:12     ` Eric Wong
2013-05-28 18:56 ` Troex Nevelin

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=op.wxs3k6kjaya692@earth.site \
    --to=adymo@pluron.com \
    --cc=mongrel-unicorn@rubyforge.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).