ASP. NET upgrade capability (1)

Scalability is always associated with performance in my last topic, but in fact they are totally different. In
In the Performance section, I have talked about caching, which is one of the biggest improvements to scalability. Therefore, I (the author) is thinking that I have to find some of its
Some of its contents are discussed in this section.

First of all, this system has its own characteristics to Improve the Performance in the multi-processor and string environments. For example, the session state can be
Server sessions. In this way, even if you do not
I have thought about how fast the traffic will increase, or I can easily add more network servers.

There are also some things called "web Garden" that I don't fully understand. However, they can help multi-processor machines
More work for a single processor. I think it is a very novel idea, but some people think they will not use this function.

Therefore, you already have tools to build a perfect web farm, but how can you keep them running? Of course, ASP. NET runtime will monitor
And manage processes. When a vulnerability or deadlock exists, the runtime is automatically closed, but you only need to wait and it will be restored. Before the old version is disabled, a new version
Will be started at the location of the old version to overwrite the old version. Runtime then directs new commands to the new working process, rejects old commands, and closes them. Because there is a replacement
In the end, the user will not find any changes.

After introducing the high performance of ASP. NET, I will introduce several examples below.