This is a disk IO issue, not running out of connections, setting 190 is
pointless, 16k is more then enough, no more then 2 workers per cpu, I see 12
workers so do you have enough cpu's to cover that?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,251186,251210#msg-251210
__
When i said "my bandwidth output looks like its very jumpy". on a 1gig per
second connection my output jumps up and down 10% (100mb) used then it will
jump to like 40% (400mb) and it changes so much before when i had less
traffic it used to be a very stead and stable 400-500mb output and hardly
eve
Now i am clueless because i dropped keepalive requests i also dropped any
send_timeout values.
And this is what my bandwidth output looks like its very jumpy when it
should not be and my page loads are very slow even on static files like
html, mp4, flv etc and considering its nginx that delievers
Hi!
On Wed, 2014-06-25 at 15:35 +, Michael Rauch wrote:
> Hello,
>
>
>
> we facing the same issue with version “nginx-1.4.7-1.el6.ngx.x86_64”.
>
> Did anyone find a solution?
>
>
>
> Regards,
>
>
>
> Michael Rauch
>
SysAdmin's view...
It does to some extent depend on how NFS is
c0nw0nk Wrote:
---
> Could it be possible my server slows down because all connections are
> in use ?
No, it's a recycling and auto-tuning issue as far as I can see, have you
determined at which value you noticed the difference or is this value s
Could it be possible my server slows down because all connections are in use
?
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,251186,251201#msg-251201
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
Maxim Dounin Wrote:
---
> Hello!
>
> On Thu, Jun 26, 2014 at 09:41:15AM -0400, c0nw0nk wrote:
>
> > So i spent a while on this one and turns out the problem is a little
> > function in nginx's core called "worker_rlimit_nofile".
> >
> >
> > Bu
Hello!
On Thu, Jun 26, 2014 at 09:41:15AM -0400, c0nw0nk wrote:
> So i spent a while on this one and turns out the problem is a little
> function in nginx's core called "worker_rlimit_nofile".
>
>
> But for me on windows (i don't know if it does it for linux users too.)
> grinds my site down to
Hello,
I recently stumbled into a situation where I could not seem to find a way
of disabling unwanted errors being logged.
Configuration:
location / {
try_files $uri $uri/ @https;
}
location @https {
return 301 https://$host$request_uri;
}
That works well for locations like '/foo' wher
I don't know how you would try to replicate this issue because i have
thousands upon thousands of files being accessed simultaneously without me
setting that value insanely high pages and access to thing take 10 seconds
and more even timeouts was occurring but as soon as i set that value it all
sto
c0nw0nk Wrote:
---
> Well without a value everything is very very slow. With a value its
> nice and fast.
Interesting to know, the Windows design and other portions scale
automatically between 4 API's to deal with high performance while offloadin
I recon its because i have media sites with lots of files and pictures
videos content etc so i need it to be a large limit.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,251186,251192#msg-251192
___
nginx mailing list
nginx@nginx.org
http://
Well without a value everything is very very slow. With a value its nice and
fast.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,251186,251188#msg-251188
___
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx
The way things have been redesigned, worker_rlimit_nofile has no purpose
anymore, it's best not to set any value.
Posted at Nginx Forum:
http://forum.nginx.org/read.php?2,251186,251187#msg-251187
___
nginx mailing list
nginx@nginx.org
http://mailman.ng
So i spent a while on this one and turns out the problem is a little
function in nginx's core called "worker_rlimit_nofile".
But for me on windows (i don't know if it does it for linux users too.)
grinds my site down to a halt unless you increase its value.
Why does it do this ?
http://nginx.org
On Thu, Jun 26, 2014 at 01:01:13AM -0400, RandysPants wrote:
> If I add:
> location / {
> deny all;
> }
>
> It blocks just fine I just cant figure out how to allow /folder2
location /folder2 {}
This does assume there are no other location{} blocks; and it does allow
more than just /folder
16 matches
Mail list logo
