I tested the scenario (proxy termination case, downstream is HTTPS and upstream is HTTP) with a 64KB file using the OpenSSL engine and observed that the throughput is very low for small files (64KB). I have attached the proxy and backend server configurations. Please review the configurations and guide me if any additional configurations are needed to boost performance.
For single process NGINX, I am getting 0.11 GBPS with 256 TPS.
@fero-majeeth During the stress test, check the CPU consumption of the tengine process. It is possible that gzip compression consumes more CPU and the CPU is fully utilized.
Hi Team,
I tested the scenario (proxy termination case, downstream is HTTPS and upstream is HTTP) with a 64KB file using the OpenSSL engine and observed that the throughput is very low for small files (64KB). I have attached the proxy and backend server configurations. Please review the configurations and guide me if any additional configurations are needed to boost performance.
For single process NGINX, I am getting 0.11 GBPS with 256 TPS.
OpenSSL version: 1.1.1q NGINX version: release-1.22.0
Proxy configuration:
events { use epoll; worker_connections 65536; multi_accept on; accept_mutex off; }
http { keepalive_timeout 300s; connection_pool_size 1024; keepalive_requests 1000000; access_log off;
}
Backend Server:
events { use epoll; worker_connections 65536; multi_accept on; accept_mutex off; }
http { keepalive_timeout 300s; connection_pool_size 1024; keepalive_requests 1000000; access_log off; server { listen 8000 default_server; root /var/www/html; index index.html index.htm index.nginx-debian.html; servername ; location / { try_files $uri $uri/ =404; } } }