In IIS6, each site has its own application pool, and in the application pool there is a application that runs the site, and by default all of the site's applications are assigned to the default application pool.
Of course, we can create a new application pool and then change the application pool where the site resides. Add an application pool: Modify the application pool where the site resides under the Home Directory tab of the properties of the Web site: View results: Because all sites are in the same application pool by default, they all share the same w3wp process. The maximum number of processes for the Web garden is set to 1 by default in the default application pool.
Now that we have access to three sites in the default application pool, we can see that only one w3wp process in the process manager is running, which validates the conclusions we mentioned above. We can also use the command-line tool to see what: are running. Then let's test the use of the Web garden first we set the largest number of worker processes in the Web garden of the default application pool to 5: and then, We made 10 visits to 3 sites in this application pool, and finally we looked again at the number of worker process w3wp: from the results above, after modifying the Web garden, access to the sites in the application pool, generating up to 5 w3wp processes, Is the value we set above, at which point the 5 w3wp processes can make the user's request at the same time. Note: There is a quarantine between the 5 w3wp processes here, so the data between them cannot be shared, such as session, so if a user logs in at the session and logs his login information, And then a request in the back of his request is no longer handled by the original W3WP work process will cause the user to drop the status of the line. Next we'll check to see if the above 5 w3wp really belong to the default application pool because, after a while, a w3wp can consume a lot of memory, so at this point, we need to recycle the worker process, The time to reclaim can be set in the properties of the application pool: when the recycle time is reached, or after we manually click the Recycle worker process, IIS re-creates the same number of worker processes, allowing the new worker process to replace the old worker process to process the request. Then end the old work process. For example, we currently have 5 w3wp processes running at the same time in this default application pool, and we recycle manually, at which point IIS creates 5 new w3wp processes to process the request, then ends the original 5 processes, and the process can be seen in the following figure: above is the case in IIS6, let's take a look at the w3wp work process in IIS7: in IIS7, each time we create a new Web site, the default will be the creation of an application pool, Then the application pool will contain our application in the application pool right-click on its advanced settings to see the maximum number of worker processes in an application pool in IIS7 is also 1, so, in general, we visit a website on IIS7, Only generates a W3WP worker process, regardless of the number of requests, that is, n the site will have a maximum of nW3WP process. When we modify the maximum number of working processes to 3 o'clock, we can find that the results are the same as in IIS6, with a maximum of 3 corresponding w3wp work processes. from the above can see the resulting 3 work processes are belong to T3 this site, in IIS7 also provides command line tool operation IIS, this tool in IIS7 name is Appcmd.exe, it is in the IIS7 installation directory, generally in the following location: using Appcmd to monitor the w3wp recovery process, you can get the same results as in IIS6: if the error occurs while running the command, it may be due to insufficient permissions. As soon as you right-click Run cmd as an administrator, execute the command.
The w3wp work process in IIS6 and IIS7
