Administering an ISP Installation

Process Accounting and Process Throttling

In addition to throttling static content, you can throttle processes on Web sites. If one of your customers is consuming too many resources, to the point that other Web sites are slowed down or otherwise affected, you might want to restrict the amount of resources this customer can consume. To do so, you must first measure resource consumption, in order to see which site is consuming too much. Then, limit its amount of resources. IIS 5.0 comes with two new features to help you do this:

Process accounting logs the CPU time and other resources used by applications.
Process throttling limits the amount of resources a Web site can consume.

Process accounting and process throttling work only for applications run out of process. You cannot activate accounting for in-process applications, or for applications run in the new IIS 5.0 out-of-process pool.

You can track the CPU time for applications, log information, and put throttling limits on the site, if necessary. Generally, process accounting and process throttling apply to an entire site and cannot be targeted toward any individual application, unless only one application is running on the site. If you have more than one application running on the site, you can target a specific application by writing a script in the metabase, using the appropriate property:

CpuAppEnabled Enables process accounting and throttling for an out-of-process IIS 5.0 Web Application Manager (WAM) application.

CpuCgiEnabled Enables process accounting and throttling for a CGI application.

For details, see the “CpuAppEnabled” topic in the IIS 5.0 online product documentation. For information about activating process accounting and process throttling, see the “Tracking Processor Use” and “Throttling Processes” topics in the IIS 5.0 online product documentation.

See the following: