From: Eric Wong <normalperson@yhbt.net>
To: unicorn list <mongrel-unicorn@rubyforge.org>
Subject: Re: Increassing timeouts
Date: Tue, 15 Jan 2013 19:44:08 +0000 [thread overview]
Message-ID: <20130115194408.GA30869@dcvr.yhbt.net> (raw)
In-Reply-To: <DDA1C0EF-0397-43AE-B783-832E4121C515@gmail.com>
Manuel Palenciano Guerrero <mpalenciano@gmail.com> wrote:
> Hello there
>
> We use Unicorn in all of our production/staging web-apps, and we are
> very happy with it. But we also have one of the apps talking to a
> web-service via SOAP, and this web-service now takes longer than usual
> processing requests. To solve this situation we have increased the
> time-outs for unicorn and nginx (proxy_read_timeout and
> proxy_connect_timeout) from 30 to 120, and everything works fine this
> way (although I don't like it).
>
> My question is: having increased the time-out to 120 means this app is
> now considered slow (or sleepy) and should be run by Rainbow ? or is
> 120 still ok for Unicorn ?
As usual, it depends. If clients hitting other endpoints are able to
access your site, you're fine...
But seriously, who will wait 120s for a website to load?
_______________________________________________
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
next prev parent reply other threads:[~2013-01-15 19:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-14 15:42 Increassing timeouts Manuel Palenciano Guerrero
2013-01-15 19:44 ` Eric Wong [this message]
2013-07-09 15:15 ` Troex Nevelin
2013-07-09 15:15 ` Troex Nevelin
2013-08-03 6:32 ` Eric Wong
-- strict thread matches above, loose matches on Subject: below --
2013-01-16 15:17 Manuel Palenciano Guerrero
2013-01-16 18:53 ` 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:
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=20130115194408.GA30869@dcvr.yhbt.net \
--to=normalperson@yhbt.net \
--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).