same issue, need to know how!
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,206345,258760#msg-258760
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
I have a python application hosted under gunicorn that is expected to have long
lived requests.It works just fine if we hit the application directly; however,
we want to have nginx in front of it and are having issues with 504 errors.
I found some settings on-line that seem to be what we want to
On Friday 08 May 2015 12:01:47 zilog80 wrote:
> can i bypass the resolver test in configtest?
>
No.
wbr, Valentin V. Bartenev
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
can i bypass the resolver test in configtest?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,258721,258753#msg-258753
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
First off, thanks to all who contributed to this thread. I must admit I did
not understand much of it, however as someone plagued by this bug (we have a
bunch of cherrypy REST servers talking to iOS and Android clients and have
seen a lot of those fallback errors), I must admit I'm a bit of a loss
Right, thanks.
Btw, we used another nginx official doc for optimization and the most
effective optimization parameter was tweaking the backlog from default 512
to 4096 in nginx listen directive.
http://nginx.com/blog/tuning-nginx/
Regards.
Shahzaib
On Fri, May 8, 2015 at 6:18 PM, Valentin V. Ba
On Friday 08 May 2015 18:15:59 shahzaib shahzaib wrote:
> Hi Valentine,
>
>
> >>What's really important is the connections that nginx cannot close. The
> >>active ones.
> >>How long the connection is active depends on the request processing time.
>
>
> Thanks for pointing that to me. Nginx s
On Friday 08 May 2015 18:05:51 shahzaib shahzaib wrote:
> Well, reducing keepalive_timeout and increasing the values of
> worker_connections resolved our issue. Following is the reference we used
> to tweak nginx config :
>
> http://blog.martinfjordvald.com/2011/04/optimizing-nginx-for-high-traffi
Hi Valentine,
>>What's really important is the connections that nginx cannot close. The
active ones.
How long the connection is active depends on the request processing time.
Thanks for pointing that to me. Nginx serving around 800Mb of mp4 files
but the problem is we're unable to track requ
Well, reducing keepalive_timeout and increasing the values of
worker_connections resolved our issue. Following is the reference we used
to tweak nginx config :
http://blog.martinfjordvald.com/2011/04/optimizing-nginx-for-high-traffic-loads/
Thanks.
Shahzaib
On Fri, May 8, 2015 at 4:42 PM, Valent
On Thursday 07 May 2015 18:38:23 shahzaib shahzaib wrote:
> Hi,
>
> It looks like we made the false calculation based on entertaining
> concurrent connections per seconds and worker_connections limit was set to
> be very low. I've increased this limit to 16000 and issue looks to be
> fixed. Here
Hello!
On Thu, May 07, 2015 at 02:28:12PM -0400, 173279834462 wrote:
[...]
> It turns out that the problem is "security.ssl.enable_ocsp_stapling", which
> is
> "true" by default. If I disable it, then FF loads the web sites. If I
> re-enable it,
> then FF complains again:
>
> > Secure Connect
On Thursday 07 May 2015 23:27:44 shahzaib shahzaib wrote:
> Hi,
>
>There are some tweaks required to nginx configurations. If the same
> image which usually takes second to response can takes upto 10-20 seconds
> to load, the wide guess would be exceeding concurrent connections at peak
> traff
13 matches
Mail list logo
