IIS6 architecture model: W3SVC introduction, iis6 architecture model w3svc

IIS6 architecture model: W3SVC introduction, iis6 architecture model w3svc

IIS6 architecture model: W3SVC Introduction

1. Overview

Unlike IIS 5.0W3svchas been removed from the inetinfo.exe ProcessIt runs as an independent process. Based on the configuration data settings,W3SVCResponsible for creatingWorker Process (W3Core).

W3SVC also monitors the running status of a worker (W3Core. (PS: W3Core, also known as Worker process.exe or w3wp.exe

As an independent process, W3SVC does not contain any third-party user code. Therefore, it will not be affected by web site faults and is always in a stable running state. On this premise, W3SVC can stably monitor the running status of web websites and take actions as necessary.

Based on this policy, the server can monitor and restart applications based on user-specified parameters..

2. Performance monitoring

In the IIS6 Information Service Manager, set the protection level of the application as follows, for example:

(Figure) Performance Configuration

Open the path to the preceding figure: Start Menu> Administrative Tools> Internet Information Service Manager> application pool> properties.

Here, IIS provides four performance monitoring functions:

Monitoring of idle timeout. If the worker process remains idle, W3SVC closes the worker process when the idle time reaches the set value.

Ü Request queue restrictions. If the user's request to the working process reaches the set upper limit, W3SVC will restrict the user's request.

Ü CPU monitoring. If the CPU usage of a worker exceeds the configured upper limit, W3SVC takes corresponding measures based on the IIS configuration information.

Ü Web garden. The web garden will be detailed in the following sections.

3. Application program running status monitoring

In the Internet Information Service Manager, the configuration of application program running status monitoring is as follows:

(Figure) running condition configuration

Choose Start> Administrative Tools> Internet Information Service Manager> application pool> properties.

Here, IIS provides four functions to monitor the running status of the application pool:

Ü Ping. W3SVC performs the Ping operation on the worker thread within the specified interval to obtain the status information of the worker thread.

Ü quick failure protection. If a certain number of worker processes fail during the specified period, W3SVC disables the application pool.

Ü start time limit. The worker process must start within the specified time.

Ü disable the time limit. The worker process must be disabled within the specified time.

4. Recycle application pool

In the Internet Information Service Manager, the configuration of application pool recycle is as follows:

Here, IIS provides four recycling methods:

Ü you can set the time interval for the recycle worker process.

Ü the process can be recycled based on the number of requests to the working process. Once the number of user requests to the working process exceeds the set value, the system will recycle the application pool.

Ü timed recovery.

Ü reclaim based on memory consumption.

When an application fails, W3SVC is notified to perform process recovery.

W3SVC starts a new working process. The old worker process continues to execute unfinished user requests, but does not receive new user requests.

Communicates with new and old working processes to synchronize application status information. After the new worker completely obtains the application state information in the old worker, it notifies W3SVC that it is ready to receive http requests from the user.

The old process completes its pending requests and closes normally, or if the configured time limit, number of requests, and set time schedule are reached, or the process is terminated explicitly after the specified memory usage limit is reached.

The new worker starts to work and receives http requests from users.