The usual website 100 concurrent, big?

I tested it this way:
Ab-n 1000-c 100-w http://www. **.cn/index.php >>d:/1.html
This is a small amount of concurrency, right?

Reply content:

I tested it this way:
Ab-n 1000-c 100-w http://www. **.cn/index.php >>d:/1.html
This is a small amount of concurrency, right?

Look at your definition of size.
Let's take a rough look at
The average website home page Peak 100 concurrent estimate, assuming your mean response time is 200ms, that is the QPS.
If the daily average is 1/4 of the peak (assuming that the early morning visits are close to 0 and the mean is pulled down), it is a day mean of a QPS.
One day of PV = 125x24x3600 = 10800000 = 10 million
Do not count the PV, not a small station it.

Of course, the actual situation cannot be counted. Concurrency is not necessarily the home page, home Static is also a common way to reduce PHP concurrency. A lot of specific plans, not detailed description.

I feel it is not small, 1 floor answer is very good,

1 days = 86,400 seconds
1 sec 100 concurrency
8640000 requests a day
1 day 8.4 million reads

The data is beautiful, but stress testing is usually done with database operations.
If there were no database operations, the single-theory implementation of the QPS would have no meaning at all. Any language is over 500.
Plus distributed deployment, there's no limit at all.

It is wrong to say that the data given by the master does not contain "1 seconds 100 Concurrency".
Assuming that the master presses ENTER, the data is
Complete requests:1000
Failed requests:999

That would be tantamount to the question that the Lord did not provide any information at all.
For the Lord, I can only say that it has been pulled black

