Which OS? What NIC? You also have to consider the traffic source, is it
known capable of of saturating the NIC on your server?
On Fri, Jan 6, 2017 at 10:24 AM, MrFastDie
wrote:
> Hello,
>
> the last days I played a little with the NGINX settings and the tcp stack
> to
> test the best performance
Dear all,
The error message:
2017/01/05 18:28:49 [error] 32633#32633: *3 upstream prematurely closed
connection while reading response header from upstream, client:
xxx.xxx.xxx.xxx, server: server_hostname.domain.ltd, request: "POST
/SOGo/connect HTTP/2.0", upstream:
"https://ip_server:port_n
Hello,
the last days I played a little with the NGINX settings and the tcp stack to
test the best performance. I used direct connection between my testing
machine and my server using a cat5e cable.
My nginx.conf can be found at pastebin: http://pastebin.com/rRAEwvNc
My sysctl.conf also provides lo
mex Wrote:
---
> grey rules means they are deactivated
>
>
> i'm gonna write a blog on how we use spike + doxi-rules in our
> setup, but it will take some time.
That's cool look forward to it also the rules on spike I think need updating
with t
grey rules means they are deactivated
i'm gonna write a blog on how we use spike + doxi-rules in our
setup, but it will take some time.
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,271695,271844#msg-271844
___
nginx mailing list
nginx@ng
