Azure advanced strategy | smooth operation of applications to prevent overloading. You have a good method. azure advanced

Azure advanced strategy | smooth operation of applications to prevent overloading. You have a good method. azure advanced

There are many things in the world, regardless of transportation, housing and building, or even computer programs, there is a theoretical maximum in terms of capacity.

For example, a train is normally like this. Sit comfortably, read a book quietly, and look up thoughtfully beyond the window from time to time, full of literary fan:

But if so, whether it is comfortable or not. What's important is, is it unsafe ......

This is also true for computer programs. Many programs normally have the maximum capacity in many aspects, such as the number of CPU cores that can be used, the number of lines of content that can be contained in the generated file, or the number of capacity bytes, even the number of network connections that can be accepted at the same time is limited.

This capacity ceiling is mainly used to ensure that the program runs smoothly within a reasonable range to meet users' expectations. If you do not limit it, it will often cause a lot of unnecessary troubles.

For example, a live broadcasting software needs to reserve 500 kbps (0.5 mbps) bandwidth for each user to provide the live video service to the user, and the server they use, each server has a maximum network bandwidth of 1000 mbps. A simple mathematical operation tells us that in theory, a single server can only provide services for 1000 users 0.5 = 2000 users at the same time. If no restrictions are imposed and more users are allowed to connect to the same server, the viewing experience of each user cannot be guaranteed.

So what is the maximum number of connections for Azure Web applications?

Note that Azure Web application services have similar restrictions when hosting websites or applications. However, note that the limit is not bandwidth, but external connections.

Depending on the size of the Instance used by the Web application service, there are the following restrictions on the number of external connections:

When the maximum number of external connections is exceeded, a socket exception occurs in the Azure Web application. Note that this restriction applies to a single Web application instance. That is to say, if multiple applications are hosted through the same Web application instance, the total number of external connections of all applications is subject to the above restrictions. For more information, click here.

 

So what should I do after reaching the upper limit?

Here is a simple example! If a small instance exceeds the upper limit, you can upgrade it to a medium or large instance. If the instance exceeds the upper limit, you can directly upgrade it to a large instance. This operation can be performed in the Azure management backend. Select the instance scale as required.

This "Scale-Up" approach is called Scale-Up ), it can be simply understood as adding more resources such as CPU, memory, and hard disk to the servers running Web applications.

What should I do if I have already used the largest instance and the number of connections is frequently exceeded?

In this case, you can Scale Out to add more servers and use multiple servers to simultaneously host our Web applications. This operation can also be performed in the Azure management backend. We can choose to use several instances as needed to run Web applications. A maximum of 20 Web applications can be selected.

Regardless of Scale-Up or Scale-Out, the changes will be applied to all applications hosted in the Web application within a few seconds.

Note that the above restrictions and scaling methods are only applicable to basic, standard, and advanced instances of Azure Web application services, because only these instances run through dedicated virtual machines, you can scale as needed. Free and shared instances in Azure Web applications run through shared virtual machines and cannot be scaled on their own. They are subject to more restrictions (because these two levels are mainly for testing and simple requirements, is not recommended in the production environment ).

There are other issues to consider about scaling Azure Web application services. For more information, see [here. For more details about the Scaling Application Service Plan, click here.

 

Visit http://market.azure.cn now