Build a high-performance. NET application to configure a high-availability IIS server-Article 4 common IIS problems: Working Process recycling mechanism (I)

Through the popularization of the three articles, I believe everyone should have a basic understanding of IIS. Starting from this article, we will start to discuss some practical topics about IIS: how to configure IIS to ensure its performance as high as possible. Series of articles:Configuration of high-availability IIS server for building high-performance. NET Applications-Article 1: required knowledge of IISBuild high performance. NET application configuration High Availability IIS server-Article 2 IIS request processing model construction high performance. NET application configuration High Availability IIS server-Part 3 Explanation of three core components of IIS) Build high performance. NET application configuration High Availability IIS server-Part 3 Explanation of three core components of IIS) Build high performance. NET application configuration of high-availability IIS server-Article 4 iis faq: Working Process recycling mechanism) in this article we mainly talk about "Working Process recycling mechanism ", let's take a look at the details. The topics in this article are as follows:Explanation of Working Process recycling mechanismTime-based recovery mechanismRecovery mechanism based on the number of requestsMemory-based recovery mechanismActivity status-based recovery mechanismExplanation of Working Process recycling mechanismIn IIS6 and IIS7 application pools, you can perform a series of configurations to control how to start and stop working processes in the pool. Reasonable configuration can make the application more available, especially when problems occur, You can minimize the loss. Through configuration, some processes in the application pool that run slowly or will fail can be quickly terminated and replaced by new processes. The recycling mechanism is different from the startup mechanism because the recycling mechanism is a relatively intelligent policy. The recycling mechanism allows a process to process the existing tasks before being recycled, the restart mechanism is forced to close. With the recycle mechanism, you can start a new process while the old process is still processing the previous request, so that the new request is processed by the new process. It is clear that when a worker process is recycled, any State stored in the process will be cleared, such as session and cache. If we want to ensure that the running status, such as session and cache, is not cleared with the Recycle of the worker process, we must use other methods to save the status, instead of directly saving it in the memory of the worker process, for example, the session can be stored in a database, and the cache can be implemented in a distributed cache. Next, let's take a look at several policies that are being recycled by the worker process, or when to start the recycle mechanism. Before explaining this, let's take a look at the configuration of the recycle mechanism in the application pool, which is IIS7's: 650) this. width = 650; "border =" 0 "alt =" 20120511114710.png" src =" http://www.agilesharp.com/Services/BlogAttachment.ashx?AttachmentID=332 "Width =" 550 "/> click" recycle "and the following page is displayed: 650) this. width = 650; "style =" display: block; margin-left: auto; margin-right: auto "border =" 0 "alt =" 20120425114734.png" src =" http://www.agilesharp.com/Services/BlogAttachment.ashx?AttachmentID=333 "Width =" 550 "/> 650) this. width = 650;" border = "0" alt = "2012020.114801.png" src =" http://www.agilesharp.com/Services/BlogAttachment.ashx?AttachmentID=334 & Quot; width = & quot; 550 & quot;/& quot; width = & quot; 650 & quot. width = 650; "style =" display: block; margin-left: auto; margin-right: auto "border =" 0 "alt =" 20120425114850.png" src =" http://www.agilesharp.com/Services/BlogAttachment.ashx?AttachmentID=335 "Width =" 550 "/> then set in" recycle ", 650) this. width = 650;" border = "0" alt = "201201_114953.png" src =" http://www.agilesharp.com/Services/BlogAttachment.ashx?AttachmentID=336 "Width =" 550 "/> as you can see, We can configure them based on many different policies, next, let's take a look at each recycling policy and specific configuration information.Time-based recovery mechanismThis recycling policy should be easy to understand, that is, to set the time to decide when or how long to recycle.Fixed collection IntervalWith this configuration item, we can set the duration of each application pool minute) to recycle resources of the worker processes in the pool. The default value is 1760 minutes, that is, one day. If our application fails before this time interval is reached, and a problem occurs, then, ISet this value to 80% of the failure time.. For example, if an application fails within 1000 minutes, it cannot be recycled because the recycle time is set to 1740 minutes later, if we let this happen, the server's resources will be exhausted. In this case, we can obtain the average failure interval through multiple data sampling. Assume that the interval is 1000 minutes. At this time, we set the "fixed-time collection interval" to 800 minutes. In some cases, this configuration can be an emergency solution to quickly handle resource leaks. However, technical personnel are required to solve the cause of site operation failure.Set the recycle IntervalAnother method to compare the data recovery is to set the data to be recycled during the day. Set as follows: 650) this. width = 650; "border =" 0 "alt =" 20120425115216.png" src = "http://www.agilesharp.com/Services/BlogAttachment.ashx? AttachmentID = 337 "width =" 550 "/> we can control the time point at which to recycle, especially when the problem is actually diagnosed. If we find that at a certain point, the site is always unable to request or use too many resources, for example, when the site access peak value), we can set it so that the resources can be recycled as soon as possible. Today, let's go to the next article!Links to articles:IISServer Load balancer-Application Request RouteArticle 1:ARRIntroductionIISServer Load balancer-Application Request RouteArticle 2: Creation and ConfigurationServer Farm IISServer Load balancer-Application Request RouteArticle 3: UseARRProceedHttpRequest Server Load balancer) IISServer Load balancer-Application Request RouteArticle 3: UseARRProceedHttpUnder the requested Server Load balancer) IISServer Load balancer-Application Request RouteArticle 4: UseARRImplement layer-3 deployment architecture Server Load balancer Principles and Practices The first article is reorganized)Server Load balancer Principles and Practices Article 2. reorganize)Server Load balancer Principles and Practices Article 3 Basic concepts of Server Load balancer-Network BasicsServer Load balancer Principles and Practices Article 4 Server group using Server Load balancerServer Load balancer Principles and Practices Article 5 Detailed description of Packet Flow During Server Load balancerServer Load balancer Principles and Practices Article 6 Health Check Mechanism details)Server Load balancer Principles and Practices Article 7 Health Check Mechanism)Server Load balancer Principles and Practices Article 8 Network Address Translation)Server Load balancer Principles and Practices Article 8 Network Address Translation(Lower)Server Load balancer Principles and Practices Article 9 Server Load balancer Advanced Technology-Session persistence)Server Load balancer principles and practices-Part 10 Server Load balancer technology-session persistence) Server Load balancer principles and practices-Part 2 Server Load balancer technology-session persistence): latency binding

This article is from the "Yan Yang Tian" blog, please be sure to keep this source http://yanyangtian.blog.51cto.com/2310974/836518