As an old dog in this world, i don't think you should ever take release
notes over config tests and further web tests (siege, wrk, ab). Nginx has
become such a versatile server starting with web and any proxy , then with
openresty and unit etc ...how can you provide proof of an upgrade path.
This i
I appreciate the suggestion but it doesn't look like this is possible to
solve with these modules. The authentication part happens as a sub-request,
and the response provided by sub request influences how the gRPC part is
handled at the top level. Unless I can figure out some way to pass
variable
I’d suggest that you use wrk2, httperf, ab or similar to run a synthetic test.
Can your site handle one request every five seconds? One request every second?
Five every second? ... is your backend configured to log service times? Is your
nginx configured to log service times? What do you see? By
Hi Maxim,
Thank you for your suggestion. I understand that enabling/disabling logging
introduces extra CPU overhead. However, I will start to monitor the listen
queue with the ss command and debug the Issue further.
Thanks,
Om
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,284757,284
>
> @all : Can someone help /point-out what i have missed in proxy_protocol
>> here?
>>
>> > I am using *NGINX 1.13.5 as a Load Balancer for one of my
>> > CUSTOM-APPLICATION *which will listen on* UDP port 2231,67 and 68.*
>> >
>> > I am trying for Load Balancing with IP-Transparency.
>> >
>> >
>>
Hello!
On Sat, Jul 13, 2019 at 09:50:50AM -0400, heythisisom wrote:
> Hi Maxim,
>
> The nginx reverse proxy and uWSGI runs on the same host. Each nginx reverse
> proxies are connected to only one single Instance of the uWSGI backend.
>
> But in the uWSGI backend, I'm running 4 workers in total
