The loadrunner output of 1.1.19 is attached, there are many connection timeout error reported by loadrunner.

My latest test show that 1.1.18 is OK , so changes between 1.1.18 and 1.1.19 make things worse in my test lab.

the os is debian squeeze 32bit, the config is :

user root root; worker_rlimit_nofile 81920; worker_processes 2; pid /secone/var/run/nginx.pid; error_log /dev/null error; pcre_jit on; events { use epoll; worker_connections 12000; multi_accept on; accept_mutex off; } http { include mime.types; default_type application/octet-stream; sendfile on; tcp_nopush on; reset_timedout_connection on; ignore_invalid_headers on; underscores_in_headers on; proxy_buffering on; proxy_ignore_client_abort on; proxy_intercept_errors on; client_header_buffer_size 16k; large_client_header_buffers 4 16k; msie_padding off; msie_refresh off; access_log off;

upstream upstream_www { server 192.168.2.3:80 max_fails=0 ; server 192.168.2.4:80 max_fails=0 ; server 192.168.2.5:80 max_fails=0 ; server 192.168.2.6:80 max_fails=0 ; } upstream upstream_www2 { server 192.168.2.254:80 max_fails=0 ; }

server {

listen 192.168.1.1:80 ; server_name _; proxy_set_header Host $http_host; location / { proxy_pass http://upstream_www2; proxy_redirect default; } }

server {

client_header_timeout 60; client_body_timeout 120; client_max_body_size 100m; client_header_buffer_size 16k; large_client_header_buffers 4 16k; proxy_buffer_size 16k; proxy_buffers 4 16k; listen 192.168.1.1:80 ; server_name www.test.com;

ssl off; keepalive_timeout 0; proxy_cache_key $scheme$host$request_uri;

location / { proxy_set_header Accept-Encoding identity; proxy_set_header Host $http_host; proxy_next_upstream error timeout http_500 http_502 http_503 http_504; proxy_cache off; proxy_pass http://upstream_www; } }

在 2012年4月27日 下午4:08，Sergey Budnevitch <sb...@waeme.net> 写道：