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
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
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
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's the mechanism i used to calculate concurrent connections/sec:
wor
Experts,
Could you please do me a favor in order to solve this problem ?
Regards.
Shahzaib
On Sat, May 2, 2015 at 3:32 PM, shahzaib shahzaib
wrote:
> Hi,
>
> We've been running nginx-1.8 instance on one of our media server to
> serve big static .mp4 files as well as small files suc
Hi,
We've been running nginx-1.8 instance on one of our media server to
serve big static .mp4 files as well as small files such as .jpeg. Nginx is
serving well under 13K connections/sec with 800Mbps outgoing network load
but whenever requests exceed 15K connections, nginx gets halt and 'D'
sta
