I built nginx-1.22.1 myself with the same OpenSSL-3.0.2 which was on
previous nginx-1.21.24
Both variants work same-same
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,295740,295771#msg-295771
___
nginx mailing list -- nginx@nginx.org
To uns
I moved onto v1.21.1
But result is the same -- for many workers not all parallel/concurrent AB
sessions are closed.
Any idea or hint?
Thanks
Yan
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,295740,295769#msg-295769
___
nginx mailing list -
Regarding problem TLS-session-close itself -- There is No any errors nor in
error-log nor in access-log.
I'm going to try the 1.22
"Our" NGINX-1.21 has been build from sources with OpenSSL-3.0 -- because we
need KTLS introduced in OpenSSL-3.0.
Q: Does the 1.22 already built with OpenSSL-3.0 --
just add "Follow Topic".
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,295738,295745#msg-295745
___
nginx mailing list -- nginx@nginx.org
To unsubscribe send an email to nginx-le...@nginx.org
THANKS Sergey!!! Clear. Best regards.
Yan
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,295739,295742#msg-295742
___
nginx mailing list -- nginx@nginx.org
To unsubscribe send an email to nginx-le...@nginx.org
Using NGINX-1.21.6 as TLS test-server with remote Apache-Benchmark(AB)
test-client
Both Server and Client are on Ubuntu20.04
For >6 workers on NGINX and >16 concurrent sessions AB sessions (ab -n400
-c32 https://)
a couple of test-sessions are not closed and AB reports timeout for them.
TCPDUMP an
When/WhatFor "master process" is acting (vs worker)?
Is it involved in data-traffic performance?
Could it be overloaded by agressive traffic or "stays in ~idle"?
Thanks
Posted at Nginx Forum:
https://forum.nginx.org/read.php?2,295739,295739#msg-295739
___
The documentation gives an worker_cpu_affinity example with BINARY Bit-mask
with 1word-per-1cpu
Is it possible to give a HEX-mask like 0xf0f0 instead long-long BBIN mask
I have 96 CPUs and would like to use last CPU-numbers in the affinity.
How to do that?
Thanks
Posted at Nginx Forum:
https://f