liangrubo Wrote: ------------------------------------------------------- > after a long delay(about 1 second after it got response from the client --- typo, "response" should be "request"by liangrubo - Other discussion
after more experiments, it seems nginx is experiencing some kind of tcp bottleneck, it sometimes try to connect(send SYN packet) to uwsgi after a long delay(about 1 second after it got response from the client). I also tried to start another nginx instance on the same server, which didn't have other traffic except for my tests, this nginx instance worked without any problem. Only the nginx insby liangrubo - Other discussion
Thanks for your reply. It shouldn't caused by disk write load. tcpdump gives more information: uwsgi actively close the tcp connection with nginx after sending the response, but the close takes too long to finish: uwsgi send FIN packet to nginx, nginx respond with ACK packet, but nginx sometimes sends its FIN packet long(about 1 second) after it sends the previous ACK packet (ACK for uwsgi FIN)by liangrubo - Other discussion
Hi folks, I have nginx reverse proxy to an uwsgi(on the same server). I got slow response from computer in the same LAN sometimes. Here is the information on one typical request I got from uwsgi and nginx log: time for handling the request logged by uwsgi: 0.1622s time logged in nginx access log: 0.421s time seen from the client(time wget ....): 2.1s tcpdump(on the server) tells nginx sendsby liangrubo - Other discussion
Sorry, some of my previous description is not correct: we were servering the static files on port 81 with nginx, static file serving becomes faster when we change it to be served by nginx on port 80, it seems that communication between nginx on port 80 and port 81 is the bottleneck, how can we resolve this issue?by liangrubo - Nginx Mailing List - English
Hello, we meet similar problem. if we set "multi_accept off;" and "accept_mutex on;", it sometimes took 3 or 9 or even 21 seconds to connect to nginx on port 80 from the same server. if we set "multi_accept on;" and "accept_mutex off;", we can connect to nginx on port 80 instantly but it may take long to get the response (more than 3 seconds for small csby liangrubo - Nginx Mailing List - English