Freigeben über


CpuLimitProcStop

This property specifies the percentage of CPU time, in 1/1000ths of a percent, that all isolated processes on the Web server may occupy during a given process accounting interval (specified by CpuResetInterval). If the isolated processes attempt to occupy more CPU time than specified in CpuLimitProcStop, IIS halts all isolated processes on that site affected by Process Throttling. Processes terminated due to limit overruns will not be allowed to restart until the next CPU interval reset. Any limit overrun will be recorded in the Windows Event Log, and, if process accounting is enabled, in the IIS log as well.

If CpuLimitProcStop is set to 0, or a value greater than 100,000 (100 percent), IIS will not stop the process. However, one of the other process throttling properties, such as CpuLimitLogEvent, CpuLimitPriority, or CpuLimitPause, could generate a response from IIS if a CPU limit is exceeded.

Note

Because process accounting in IIS uses Windows Job Objects to monitor CPU times for an entire process, process accounting will log and throttle only applications that are isolated in a separate process from IIS.

Process throttling and process accounting are independently controlled by several other metabase properties. In order to enable process accounting you must set CpuEnableLogging (which is a member of CpuLoggingMask) to TRUE, and set at least one other CpuLoggingMask property to TRUE. It is also necessary to set at least one member flag of the CpuLoggingOptions, set CpuLoggingInterval to a nonzero value, and set either CpuAppEnabled or CpuCgiEnabled, as appropriate, to TRUE.

To properly activate process throttling, CpuLimitsEnabled must be set to TRUE, and at least one of the following properties should be set to TRUE: CpuLimitLogEvent, CpuLimitPriority, CpuLimitProcStop, or CpuLimitPause.

ms525381.alert_caution(en-us,VS.90).gifImportant Note:

Applications that do not have process throttling enabled do not contribute to the total CPU time, for the purposes of calculating CPU limit overruns.

Schema Attributes

Attribute Name

Value

ADSI/WMI Data Type

DWORD

ABO Data Type

DWORD_METADATA

Schema Default

0

Internal Default

null

Upper Bound

Not specified

Lower Bound

Not specified

Internal ID

2151

Friendly ID

MD_CPU_LIMIT_PROCSTOP

Property Attributes

INHERIT

User Type

IIS_MD_UT_SERVER

Configurable Locations

You can configure this property at the following locations in the IIS metabase.

Metabase Path

IIS Admin Object Type

/LM/W3SVC

IIsWebService

/LM/W3SVC/n

IIsWebServer

Flags

There are no flags for this property.

Requirements

Client: Requires Windows 2000 Professional, or Windows NT Workstation 4.0.

Server: Requires Windows 2000 Server, or Windows NT Server 4.0.

Product: IIS

See Also