1 the so-called dozen of words, is a good answer!!

3000 people access a pure static file at the same time, the static file size is 28K, then the maximum theoretical value of instantaneous request flow is 3000x28K≈82M. However, this value is only the theoretical maximum traffic in an instant, because your site will not have 3000 visitors every second of every second, but the number of visitors over a period of time. If it is really at least 3000 people per second access, then your server uplink bandwidth must be at least 82×8 = 656M (multiplied by 8, because the rate we say is not the same as the rate operators say, conversion units are different), so it seems that the cost is quite high.

However, the actual request bandwidth is much lower than 656M for the following reasons:

  • User traffic is spread out, not 3000 people per second;
  • Browsers cache static pages, so some of those 3000 users actually load requests directly from the local cache instead of requesting a remote server.

To know, the uplink bandwidth of the server is very expensive, according to the above calculation method, even if a discount, your server fixed bandwidth 100M words, the cost of light bandwidth will be nearly 7000 yuan a month.

So the general small and medium-sized website server uplink bandwidth 100M is very large, in view of your visitors are not fixed, I give you advice is:

  • CDN cache is used at the front end. If static files are not updated for a long time, the cache time can be set to a long time, such as one month.
  • Choose low configuration for the back-end ECS, and do not choose fixed bandwidth (choose charging by traffic, bandwidth is 5M is enough).

With this configuration, higher concurrency can be tolerated, let alone 3000 concurrent users. CDN itself acts as a load balancing Angle, and CDN nodes spread all over the country, enabling users to “read” static resources nearby.

2. Other netizens’ answers

Missing L211: Look everyone is talking about ×8, I think there is a misunderstanding, not the operators to ×8, this is just a difference in daily usage, one is the unit of bandwidth, we use M, the other is the unit of speed, we use Mbps. In daily life, we say that the download rate is used to Mbps, and because the unit of Mbps is often simply said to be how much the download speed is M, the so-called ×8 concept came into being. Later, because of some intentional misleading, the public’s resentment for false bandwidth was amplified, and nothing more, in fact, it is only the unit conversion. A lot of people still think of light years as a unit of velocity, something like that.

Guiren Agricultural Science and Technology: Concurrent access 3000, if is a medium-sized site unless there is a network of malicious attacks, if not impossible, ordinary 3000 visitors, even under the same time, it is impossible to accurate to the second level of access at the same time, so suggest adjusting the CDN load balancing, and bandwidth to 5 m, more than 3000 visitors can guarantee a short period of time, Note not concurrency.

First, put your static files on OSS. The advantage is that when the client requests static resources through OSS traffic, not through the server, the speed is fast. Then choose to pay by volume request traffic fee of 5.1g. Ecs configuration 2 core 8G, no need to buy additional data disk, use 50m bandwidth also choose to pay 5 cents 1g, enough to use. Direct release of resources at the end of activities to save costs