IIS Metrics---Web test critical counters

Total number of successful lookups in the /internet information Services global/file cache Hits% file cache.

/process (inetinfo)/private Bytes The current number of bytes that the Http/asp service has allocated but cannot share with other processes. If the value is always large and increasing, it is possible that the server-side object is leaking.

/process (inetinfo)/% Processor time displays the processor times used by the threads of the Inetinfo process

/Process (inetinfo)/page faults/sec The total ratio of error pages processed by the CPU. Page faults/sec does not distinguish between soft and hard page faults, but can compute these errors. Page Faults/sec is the rate at which page faults by the threads

/process (inetinfo)/thread the number of threads created by the Count Web server process.

/server/bytes transmitted/sec The number of bytes the server has sent on the network.

/Web Service (_total)/current Blocked Async I/o Requests:This counter is no longer valid; Its value is always zero. The number of locks currently temporarily due to bandwidth throttling settings. The locked requirements remain in the buffer memory, unless the timeout limit is reached, or the lock will be unlocked if more bandwidth is available.

/web Service (_total)/current connections The number of connections currently established for the WEB or FTP service (the sum of Anonymous and non-anonymous users). This number is the sum of all the currently connected Web sites or FTP sites, regardless of who is selected as an example. The number of active connections to the WWW service.

/web Service (_total)/bytes total/sec: The sum of Bytes sent/sec and Bytes received/sec. The ratio of total bytes transmitted by the Web service (the sum of Bytes sent/sec and Bytes received/sec).

/Web Service (_total)/not Found errors/sec: The server cannot meet the required error rate because the requested file cannot be found. This is typically applied to the client with an HTTP error code of 404. The rate, in seconds, at which requests were not satisfied by the server because the requested document is not found.

/web Service (_total)/get requests/sec: The rate, in seconds, at which HTTP requests which use the ' Get methods ' have been to the WWW service. Ratio of HTTP requirements using the Get method 。 Although it can be used with a record sheet, get requirements are typically used for basic file retrieval or image maps.

/web Service (_total)/head requests/sec: the ratio of HTTP requirements using the head method. The head requirement usually indicates that the client is querying for file status that must be collated. The rate, in seconds, at which HTTP requests this use of the head method have been to the WWW service.

/web Service (_total)/maximum connections: The maximum number of simultaneous connections made to the WWW service since the service started. Since the Web or FTP service was started, the The maximum number of concurrent connections. This number is the maximum number of currently all Web sites or FTP sites, regardless of the selections made for "examples"

/web Service (_total)/measured Async I/O bandwidth Usage: This counter is no longer valid; Its value is always zero. The number of bytes received and sent by the WEB server, averaging within a minute. This is the measure of the total number of user traffic on the server.

/web Service (_total)/files/sec: The rate, in seconds, at which files have been sent and received by the WWW service. The rate at which the server transmits files, starting with the Web service.

in Software testing Web important counters for testing

During the test run, you should monitor the performance counters and all WEB servers for the test client. Application Center test automatically monitors HTTP performance statistics in a test run, but performance counters must be explicitly configured before the test runs.

Performance counter data is used to determine when a test client or WEB server reaches its maximum CPU usage. If the performance bottleneck of a WEB application is not a server CPU, using performance counters is the best way to determine the bottleneck location.

Some counters should be used in all tests (shown in bold in the following table), while others are only used when looking for unknown reasons for performance problems.

Performance counters for ACT clients

Object	Performance counters	Description
Processor	% Processor Time/_total	Testing the processor usage of the client
Memory	Available Bytes	Test the amount of available memory for the client.
Network Interface	Bytes total/sec	Network traffic to and from the test client.

Performance counters for Windows 2000 and IIS 5

Note that the following are counters used by Microsoft Windows 2000, IIS 5, and Microsoft SQL Server 7.0. The counters used by other versions may be different.

Logging performance counter data on a Web server can help you understand which part of your Web application is causing performance degradation.

Object	Counter	Description
Active Server Pages	Memory Allocated	The total amount of memory currently allocated by Active Server Pages. Compare this number with the Memory:available Bytes and memory:committed Bytes to determine the percentage of memory used by the ASP. If the ratio exceeds 50% during the test, there is a memory leak in one of the server-side objects.
Active Server Pages	Request errors/sec	The number of errors per second, including connection errors, compilation errors, and Run-time errors. If the number is always greater than 0, there is a problem with the test script, server configuration, or ASP script.
Active Server Pages	Requests Queued	The counter should remain close to 0. The "server is too busy" error occurs when the IIS queue length is exceeded.
Active Server Pages	Requests rejected	If the number is often greater than 0, the test load is overloaded or the server does not have sufficient resources.
Active Server Pages	Requests/sec	Number of ASP requests per second.
Internet Information Services Global	File cache flushes and file cache Hits	Compare these counters to see the ratio of cache hits to cache cleanup. A refresh occurs when a file is deleted from the cache. These global counters provide the rate at which objects are refreshed from the cache. Refreshing too slowly can waste memory. This value can be modified by adjusting the ObjectCacheTTL, MemCacheSize, and Maxcachefilesize registry settings. For more information, see Windows Resource Kit.
Internet Information Services Global	File Cache Hits%	Shows the ratio of the number of cache hits to total cache requests. For sites with static pages, this value is approximately 80%.
Memory	Available Bytes	The amount of remaining physical memory available. IIS is basically occupied by 2.5 MB, and each additional connection will occupy a KB or so on this basis.
Memory	Cache Bytes	Displays the cache size used for static files. The default setting is about 50% of the available memory, but it reduces system performance by reducing the amount of available memory.
Memory	Page faults/sec	This is the total ratio of error pages processed by the CPU. Page faults/sec does not distinguish between soft and hard page faults, but can compute these errors. Memory:pages Input/sec is the number of pages that read the disk to resolve hard page errors. The Memory:page reads/sec is the number of times the disk is read to resolve hard page errors. Compare these values to the Page faults/sec value to get a ratio. If the Page reads/sec ratio persists to 5, it may indicate that there is not enough memory.
Memory	Pages/sec