Consultation on concurrent requests

For more information about concurrent requests, see & nbsp; user & nbsp; & nbsp; page 1. a1-a1.

User page
1. a1-a10000 access at the same time/a1.htm
2. access/b1.htm/b2.htm.../b2.16.htm at the same time in b1

Explanation:
1. 10000 users simultaneously request one page
2. one user requests 10000 pages at the same time


Are these two types of servers under the same pressure? Or which one is faster? Share:
------ Solution --------------------
Check what page you are. if it is a dynamic page, the server usually has a cache. for example, a PHP page needs to be compiled and cached after compilation, concurrency is equivalent to compiling only once, and the overhead of 10000 different pages is times that of 1.
There is also the page content, the page size varies with the overhead, the number of images is also different overhead, and so on many other aspects, but the basic situation is that one page is less pressure than 10000 pages.
------ Solution --------------------
If one user requests 10000 pages at the same time, this situation exists (it should not exist)
The overhead of both is the same for servers!