Nginx toss (HTTP performance test, compared with Apache) (below)
For the second group of pictures, there are several places that need to be analyzed: The result of the production environment should be between the blue line and the red line, so there is no need to analyze it. “Logest Response Time” actually takes the time when 99% of all requests can be completed, which can shield some errors. As pressure increases, response time spikes are to be expected, but how much is acceptable? At the 2009 System Architects Conference, Tencent’s Qiu Yuepeng mentioned the “1-3-10 principle of user speed experience” in his speech in “Flexible Operation of Massive SNS Websites”: It can be simply considered that if the response time of 3 seconds is used as the standard, nginx can handle no more than 10,000 concurrent connections, and if the response time of 10 seconds is used as the standard, nginx can handle less than 15,000 concurrent connections. Of course, there may be occasions It’s different, your users can’t stand even 0.3 seconds, so that’s another story. If I assume that as long as the server does not have “connection reset”, “server no response” and other errors, as long as the content can be returned, I am willing to…