The Microsoft Commerce Server 2002 Enterprise Edition management plug-in for Oracle Enterprise Manager provides hardware and software performance monitoring of Commerce Server using performance counters and application events. These counters can help you find hardware and software bottlenecks that may be restricting the flow of data.
This chapter provides descriptions for all Microsoft Commerce Server metric categories, and tables list and describe associated metrics for each category. The tables also provide user actions if any of the metrics for a particular category support user actions.
The metrics in this category provide information about the performance of the Internet Information Services (IIS) 6.0 Server using the performance counters described below. The counters are designed to monitor server performance and cannot be configured for individual sites.
Table 8-1 Active Server Pages Metrics
| Metric | Description and User Action |
|---|---|
|
Errors Per Sec |
Average number of errors that occurred per second. |
|
Request Execution Time |
Number of milliseconds required to execute the most recent request. The value of this counter should be very close to zero. If it is not, check the code and try to determine the cause of the bottleneck that is consuming excessive execution time. |
|
Request Wait Time |
Number of milliseconds that the most recent request waited in the queue. This value should be very close to zero (less than 100 milliseconds), because this is the amount of time a request waits in the queue before it begins processing. You do not want users to experience long wait times to process their checkout transactions. If the value of this counter is high, check the code and try to determine the cause of the bottleneck that is consuming excessive execution time. |
|
Requests Executing |
Number of requests currently executing. IIS 6.0 has many threads that can simultaneously process requests. This value should be stable. Experience will help you set a threshold for a particular site. |
|
Requests Per Sec |
Rate that Active Server Pages (ASP) are processing requests. This includes both successful and failed requests. This counter provides and indication of the usage of the application. If this value is high, you may need to upgrade the hardware to handle the additional load. |
|
Requests Queued |
Requests waiting to be executed in the queue. There should not be a significant queue except at peak periods. This counter should not have a high value. It should be less than the Request Queue limit. |
|
Requests Succeeded |
Number of successfully fulfilled requests. A high value indicates a healthy system. |
|
Sessions Total |
Number of sessions that have run since the service was started. |
The metrics in this category provide information about the checks that are initiated for every request received by the server using the performance counters described below.
Table 8-2 Authentication Filter Metrics
| Metric | Description and User Action |
|---|---|
|
AuthFilter: Failed NT Authentication Checks Per Sec |
Number of failed Windows authentication checks per second. This counter is for a specific instance on the server. The value of this counter should be a nominal value and should be comparatively less than the successful authentication checks. A higher value indicates a possible credential problem with the system. |
|
AuthFilter: Successful NT Authentication Checks Per Sec |
Number of successful Windows authentication checks per second. This counter is for a specific instance on the server. The value of this counter should be high. Very low values may be of concern in cases when the traffic on the website is high, but the value of this counter is still nearly zero. Along with this counter, watch the failed authentication counter, whose value should be less than the value of this counter. |
|
AuthFilter: Token Cache Entries Active |
Current number of active token-cache entries in Windows authentication mode. This counter is for a specific instance on the server, and is reset to zero on an IISRESET or server reboot. |
|
AuthFilter: Token Cache Entries Total |
Total number of token-cache entries in Windows authentication mode. If the value of this counter is very high, increase the password cache size. It is located in the Global resource under the CS Authentication resource for the site, and is named Password-Cache Size. The default size is 10,000 objects. Another option is to set the PsObjectCacheSize property in the connection string while initializing the profiling service. After making these changes, you will need to perform an IISRESET. |
|
AuthFilter: Taken Cache Size Bytes |
Size, in bytes, of token-cache in Windows authentication mode. |
|
AuthFilter: Total Failed NT Authentication Checks |
Total number of failed Windows authentication checks. |
|
AuthFilter: Total Requests Failed |
Number of failures caused by a full filter-cache, or because an error occurred and a filter redirected to an error page. |
|
AuthFilter: Total Successful NT Authentication Checks |
Total number of successful Windows authentication checks by the authentication Internet Server Application Program Interface (ISAPI) filter. This is the total number of times the filter passed the credentials to Internet Information Services (IIS) 6.0 and returned successfully. |
|
AuthFilter: Windows Authentication Cache Hits |
Total number of user ID and password cache hits for an instance of a Windows authentication mode filter. This counter is for a specific instance on the server, and is reset to zero on an IISRESET or server reboot. |
|
AuthFilter: Windows Authentication Cache Hits Per Sec |
Number of user ID and password cache hits per second for an instance of the Windows authentication mode filter. This counter is for a specific instance on the server. You should monitor the cache hit rate and cache miss rate counters. If the cache miss rate is high in comparison to the cache hit rate, you should increase the size of your cache using the connection string parameter. |
|
AuthFilter: Windows Authentication Cache Misses |
Total number of user ID and password cache misses for an instance of a Windows authentication mode filter. A cache hit always follows a cache miss. This counter is for a specific instance on the server, and is reset to zero after an IISRESET or server reboot. |
|
AuthFilter: Windows Authentication Cache Misses Per Sec |
Number of user ID and password cache misses per second for an instance of a Windows authentication mode filter. This counter is for a specific instance on the server. |
The metrics in this category provide information about the Authentication Manager, which is called from within ASP pages using the performance counters described below.
Table 8-3 Authentication Manager Metrics
| Metric | Description and User Action |
|---|---|
|
AuthMgr: Authentication Objects Per Sec |
Number of Authentication Manager objects created per second at a particular site. A higher value f or this counter indicates a higher server load. |
|
AuthMgr: Authentication Checks Failed Per Sec |
Number of failed authentication checks per second at a particular site. The value of this counter should be a nominal value and should be comparatively less than the successful authentication checks. A higher value indicates a possible credential problem with the system. |
|
AuthMgr: Authentication Checks Succeeded Per Sec |
Number of successful authentication checks per second at a particular site. The value of this counter should be high. Very low values may be of concern in cases when the traffic on the website is high, but the value of this counter is still nearly zero. Along with this counter, watch the failed authentication counter, the value of which should be less than the value of this counter. |
|
AuthMgr: Authentication Tickets Per Sec |
Number of authenticated tickets set per second at a particular site. |
|
AuthMgr: Custom Properties Per Sec |
Number of custom properties set per second at a particular site. |
|
AuthMgr: Get_Custom Properties Per Sec |
Number of Get_Custom_Properties set per second at a particular site. The GetProperty() counter gets the custom property values from the user cookie. |
|
AuthMgr: Total Authentication Checks Failed |
Total number of failed authentication checks for a particular site. |
|
AuthMgr: Total Authentication Checks Succeeded |
Total number of successful authentication checks for a particular site. |
|
AuthMgr: Total Authentication Objects Created |
Total number of Authentication Manager objects created at a particular site. |
|
AuthMgr: Total Authentication Tickets |
Total number of authenticated tickets at a particular site. |
|
AuthMgr: Total Custom Properties |
Total number of custom properties set at particular site. |
|
AuthMgr: Total Get_Custom Properties |
Total number of GetCustom-properties set at a particular site. |
The metric in this category provides information about the status of the Commerce Server.
The metrics in this category provide information about error events generated by Commerce Server in the application log.
The metrics in this category provide information about warning events generated by Commerce Server in the application log.
The metrics in this category provide information about Data Warehouse- and Analysis-related counters. Data Warehouse performance counters are used only when importing data groups, such as DTS tasks, users, and catalogs. Therefore, the Data Warehouse performance counters need to be set up as anonymous servers.
Table 8-7 Data Warehouse and Analysis Metrics
| Metric | Description |
|---|---|
|
Catalog Import: Total Catalogs |
Total number of catalogs imported during this DTS import task. |
|
Catalog Import: Total Categories |
Total number of categories imported during this DTS import task. |
|
Catalog Import: Total Products |
Total number of products imported during this DTS import task. |
The metrics in this category provide information about the Direct Mailer and List Manager system using the performance counters described below. The Direct Mailer uses a high-performance mail generation engine to create personalized messages using the lists that you manage with List Manager. A List Manager is used to import and manage mailing lists.
Table 8-8 Direct Mailer Metrics
| Metric | Description and User Action |
|---|---|
|
DML: Direct Mail Errors Per Sec |
Number of errors returned by Direct Mailer per second. The value for this counter should be very low. |
|
DML: Direct Mail Jobs Running |
Total number of Direct Mailer jobs currently running for a particular instance. A higher value for this counter indicates a heavy server load. |
|
DML: Mail Messages Sent Per Sec |
Number of mail messages sent by all Direct Mailer jobs per second. |
|
DML: Total Direct Mail Errors |
Total number of errors returned by all Direct Mailer jobs. |
|
DML: Total Messages Sent |
Total number of mail messages sent by all Direct Mailer jobs. |
The metrics in this category provide information about the performance of EEE using the performance counters described below. The EEE consists of the evaluation core (logic), the ExpressionStore, and the ExpressionEval objects. The EEE contains an Expression Cache that caches loaded expressions, object properties, and expression results.
Table 8-9 Expression Evaluator Engine Metrics
| Metric | Description and User Action |
|---|---|
|
EEE: Evaluations Per Sec |
Number of expressions evaluated per second. Note: Displaying an advertisement or discount can cause more than one evaluation. |
|
EEE: Expression Cache Size |
Total number of expressions currently in the expression cache. The EEE engine has two internal caches: the Expression Cache and the Expression Result Cache. These EEE caches increase in size dynamically as items are added to these caches. Because these caches are dynamic, they are not customizable. To enhance the performance of the expression evaluator, it is recommended that you preload expressions into the expression cache using the LoadExpr or LoadAll methods of the ExpressionEval object. To avoid runtime expression load operations, it is recommended that you call the loadAll method in the site Global.asa file. |
|
EEE: Property Cache Hits |
Total number of property cache hits since the server was started. In addition to the Expression Cache, Commerce Server 2002 also includes an Expression Results Cache and an Expression Properties Cache. These caches grow or shrink dynamically as items are loaded or removed from them. |
|
EEE: Property Reads Per Second |
Total number of properties read by the Expression Evaluator since the server started. |
|
EEE: Total Evaluation Errors |
Total number of evaluation errors returned. |
Commerce Server includes a Product Catalog System to manage products, create multilingual and multicurrency catalogs, and provide different search methods to quickly find needed products and services.
The metrics in this category provide information about the performance of the Product Catalog system using the performance counters described below.
Table 8-10 Marketing and Catalog Metrics
| Metric | Description and User Action |
|---|---|
|
Catalog Queries Per Sec |
Number of queries made to the Product Catalog System per second. Query and FreeTextSearch record the values for the performance monitor counters. No other methods record the counters. Commerce Server 2002 implemented the same usage profile for both base catalogs and indexed view virtual catalogs to show the activities of the Product Catalog System. |
|
LRU Cache Flushes Per Sec |
Number of items flushed out of the cache per second to accommodate new items added to the cache. Records items flushed by the LRU algorithm and items flushed manually. The least recently used LRU cache counters indicate how well catalog caching is performing when catalog caching is used. An LRU cache that is performing well should have a low miss rate, a low flush rate, and a high hit rate. |
|
LRU Cache Hits Per Sec |
Number of cache hits per second for the cache. The least recently used LRU cache counters indicate how well catalog caching is performing when catalog caching is used. An LRU cache that is performing well should have a low miss rate, a low flush rate, and a high hit rate. Monitor the LRU cache counters, and tune your cache to achieve a 90 percent hit rate. |
|
LRU Cache Misses Per Sec |
Number of cache misses per second for the cache. The least recently used LRU cache counters indicate how well catalog caching is performing when catalog caching is used. An LRU cache that is performing well should have a low miss rate, a low flush rate, and a high hit rate. |
|
LRU Cache Size |
Total number of entries in the cache. Cache size can grow to 10 percent more than the size the user sets, at which time a flush occurs to return the cache size to the preset limit. LRU cache counters are grouped by site, not by the individual cache. The least recently used LRU cache counters indicate how well catalog caching is performing when catalog caching is used. An LRU cache that is performing well should have a low miss rate, a low flush rate, and a high hit rate. |
|
Predictor Client Average Prediction Time |
Average elapsed time required for a prediction to be returned. |
|
Predictor Total Client Model Loads |
Number of models loaded since the service was last restarted. |
|
Predictor Total Client Predictions |
Total number of predictions. |
The metrics in this category provide information about the performance of memory-related parameters using the performance counters described below.
| Metric | Description |
|---|---|
|
Available Bytes |
Amount of physical memory, in bytes, immediately available for allocation to a process or for system use. It is equal to the sum of memory assigned to the standby (cached), free, and zero page lists. The value should be greater than 4 Megabytes. |
|
Committed Bytes |
Amount of committed virtual memory, in bytes. Committed memory is the physical memory that has space reserved on the disk paging file(s). There can be one or more paging files on each physical drive. This counter displays the last observed value only; it is not an average. The value of this counter should not be more than 75 percent of physical memory. |
|
Page Faults Per Sec |
Average number of pages faulted per second. It is measured in number of pages faulted per second because only one page is faulted in each fault operation; hence, this is also equal to the number of page fault operations. This counter includes both hard faults (those that require disk access) and soft faults (where the faulted page is found elsewhere in physical memory.) Most processors can handle large numbers of soft faults without significant consequences. However, hard faults, which require disk access, can cause significant delays. |
|
Page Reads Per Sec |
Rate at which the disk was read to resolve hard page faults. This metric shows the number of read operations without regard to the number of pages retrieved in each operation. Hard page faults occur when a process references a page in virtual memory that is not in a working set or elsewhere in physical memory, and must be retrieved from disk. The value should be less than one page per second. If the system is actually out of memory, this is the biggest indicator of the problem. This counter is a primary indicator of the kinds of faults that cause system-wide delays. It includes read operations to satisfy faults in the file system cache (usually requested by applications) and in non-cached mapped memory files. Compare the value of Memory\\Pages Reads/sec to the value of Memory\\Pages Input/sec to determine the average number of pages read during each operation. |
The metrics in the Network category provide information about network performance using the performance counters described below.
| Metric | Description and User Action |
|---|---|
|
Bytes Received Per Sec |
Rate, in seconds, at which bytes are received over this network adapter. The counted bytes include framing characters. This counter is a subset of Network Interface\Bytes Total/sec. If a network card approaches its maximum capacity, another should be added. If this value approaches the capacity of the network, then a higher bandwidth network might be necessary. |
|
Bytes Sent Per Sec |
The rate, in seconds, at which bytes are sent over this network adapter. The counted bytes include framing characters. This counter is a subset of Network Interface\Bytes Total/sec. If a network card approaches its maximum capacity, another should be added. If this value approaches the capacity of the network, a higher bandwidth network might be necessary. |
|
Bytes Total Per Sec |
Rate at which bytes are sent and received over each network adapter, including framing characters. Network Interface\\Bytes Received/sec is a sum of Network Interface\\Bytes Received/sec and Network Interface\\Bytes Sent/sec. If a network card approaches its maximum capacity, another should be added. If this value approaches the capacity of the network, a higher bandwidth network might be necessary. |
|
Current Bandwidth |
Estimate of the current bandwidth of the network interface in bits per second (BPS). For interfaces that do not vary in bandwidth or for those where no accurate estimation can be made, this value is the nominal bandwidth. |
|
Output Queue Length |
Length of the output packet queue (in packets). Delays exist if this value is longer than two. Try to find and eliminate the bottleneck, if possible. Since the requests are queued by the Network Driver Interface Specification (NDIS) in this implementation, this will always be 0. |
|
Packets Outbound Discarded |
Number of outbound packets chosen to be discarded even though no errors had been detected to prevent transmission. One possible reason for discarding packets could be to free up buffer space. |
|
Packets Outbound Errors |
Number of outbound packets that could not be transmitted because of errors. |
|
Packets Received Discarded |
Number of outbound packets chosen to be discarded even though no errors had been detected that prevented transmission. One possible reason for discarding packets could be to free up buffer space. |
|
Packets Received Errors |
Number of inbound packets containing errors that prevented them from being delivered to a higher-layer protocol. |
The metrics in the Physical Disk category provide information about disk performance using the performance counters described below.
Table 8-13 Physical Disk Metrics
| Metric | Description and User Action |
|---|---|
|
Average Disk Queue Length |
Average of disk queue length. If the disk is not fast enough to keep up with read and write requests, requests will queue up. The acceptable queue length is a function of the number of spindles in the array. Other counters that can be used to observe disk traffic include Physical Disk: Disk Reads/second and Physical Disk: Disk Writes/second. If necessary, consider adding more physical drives, such as a Redundant Array of Inexpensive Disks (RAID) system, to increase the number of spindles that can read and write, as well as to increase data transfer rates. |
|
Disk Reads Per Sec |
Number of disk reads per second on the physical disk. This counter should be well under the maximum capacity for the disk device. To enable this counter, run diskperf –y from the command shell and reboot the computer. |
|
Disk Writes Per Sec |
Number of disk writes per second on the physical disk. This counter should be well under the maximum capacity for the disk device. To enable this counter, run diskperf –y from the command shell and reboot the computer. |
|
Percent Disk Time |
Percentage of elapsed time that the selected disk drive is busy servicing read or write requests. |
A pipeline is an extensible software framework that defines and links together one or more stages of a business process, running them in sequence to complete a specific task. The metrics in this category provide information about Pipeline performance using the performance counters described below.
| Metric | Description and User Action |
|---|---|
|
Average Execution Time |
Average execution time in microseconds for t he particular component of the pipeline. The execution time depends on the Service Level agreement with the client. It should not be high. |
|
Errors Per Sec |
Number of errors generated by the particular pipeline component per second. |
|
Errors Total |
The total number of Error Level 3 failures returned by the particular pipeline component (PIPEERRORLEV_FAIL) or FAILED HRESULT. |
|
Warnings Per Sec |
Number of warnings returned by the pipeline component per second. |
|
Warnings Total |
The total number of Error Level 2 warnings returned by the particular pipeline component (PIPEERRORLEV_WARN). |
| Metric | Description and User Action |
|---|---|
|
Creating Process ID |
Process ID of the process that created the process. The creating process may have terminated, so this value may no longer identify a running process. |
|
Handle Count |
Total number of handles currently open by this process. This number is equal to the sum of the handles currently open by each thread in the process. |
|
IO Data Bytes Per Sec |
Rate at which the process is reading and writing bytes in I/O operations. This counter counts all I/O activity generated by the process to include file, network, and device I/Os. |
|
IO Data Operations Per Sec |
Rate at which the process is issuing read and write I/O operations. This counter counts all I/O activity generated by the process to include file, network, and device I/Os. |
|
Percent Processor Time |
Percentage of elapsed time that all process threads spend using the processors. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count. The average value of this counter should be approximately 70%. |
|
Private Bytes |
Current size, in bytes, of memory that this process has allocated that cannot be shared with other processes. Memory leaks are identified by a consistent and prolonged increase in Private Bytes. This is the best performance counter for detecting memory leaks. Values greater than 60% of total physical RAM begin to impact performance, especially during application and process restarts. An optimum value for this counter is a value whichever is minimum out of 60% of physical RAM and 800 MB. |
|
Thread Count |
Number of threads currently active in this process. An instruction is t he basic unit of execution in a processor, and a thread is the object that executes instructions. Every running process has at least one thread. Thread count often increases when the load is too high. Its optimum value is expressed in the formula: 75 + ((maxWorkerThread + maxIoThreads) * #CPUs) |
|
Virtual Bytes |
Current size, in bytes, of the virtual address space the process is using. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. Virtual space is finite, and the process can limit its ability to load libraries. The value of this counter should be 600 MB less than the size of the virtual address space; either 1.4 or 2.4 GB. |
|
Virtual Bytes Peak |
Maximum size, in bytes, of virtual address space the process has used at any one time. Use of virtual address space does not necessarily imply corresponding use of either disk or main memory pages. However, virtual space is finite, and the process might limit its ability to load libraries. The value of this counter should be 600 MB less than the size of the virtual address space; either 1.4 or 2.4 GB. |
|
Working Set |
Current size, in bytes, of the Working Set of this process. The Working Set is the set of memory pages touched recently by the threads in the process. If free memory in the computer is above a threshold, pages are left in the Working Set of a process even if they are not in use. When free memory falls below a threshold, pages are trimmed from Working Sets. If they are needed, they are then soft-faulted back into the Working Set before leaving main memory. This counter measures the number of memory pages that each process uses. If the system has sufficient memory, it can maintain enough space in the working set so that IIS 6.0 rarely must perform disk operations. One indicator of memory sufficiency is how much the size of the process working set fluctuates in response to general memory availability on the server. Significant fluctuation can indicate a lack of available memory. |
The metric in this category provides information about processor performance.
| Metric | Description and User Action |
|---|---|
|
Percent Processor Time |
Percentage of elapsed time that all process threads used the processor to execute instructions. An instruction is the basic unit of execution in a computer, a thread is the object that executes instructions, and a process is the object created when a program is run. Code executed to handle some hardware interrupts and trap conditions are included in this count. The value of this counter provides an indication about the processor time utilized by the applications running on the server. A consistently very high value for this counter indicates possible problems in the code and may require some refactoring of the application. |
The metrics in this category provide information about SQL Server performance using the performance counters described below.
Table 8-18 SQL Server Statistics Metrics
| Metric | Description and User Action |
|---|---|
|
SQL Compilations Per Sec |
Indicates the efficiency of the queries that the SQL Server is running. Reduce this number to reduce the CPU load on the SQL Server. |
|
SQL Recompilations Per Sec |
Indicates the efficiency of the queries that the SQL Server is running. Reduce this number to reduce the CPU load on the SQL Server. |
The metrics in the System category provide information about system performance using the performance counters described below.
| Metric | Description and User Action |
|---|---|
|
Context Switches Per Sec |
Combined rate at which all processors on the computer are switched from one thread to another. Context switches occur when a running thread voluntarily relinquishes the processor, is preempted by a higher priority ready thread, or switches between user-mode and privileged (kernel) mode to use an executive or subsystem service. It is the sum of Thread\\Context Switches/sec for all threads running on all processors in the computer and is measured in numbers of switches. There are context switch counters on the System and Thread objects. This counter displays the difference between the values observed in the last two samples, divided by the duration of the sample interval. This counter shows the activities of the Product Catalog System. Heavy catalog queries can overload both the front-end Web server and the back-end catalog server. You can use the Commerce Server 2002 least recently used (LRU) cache to improve the performance of an overloaded Commerce Server 2002 Product Catalog System. |
|
Processor Queue Length |
Number of threads in the processor queue. Unlike the disk counters, this counter shows ready threads only, not threads that are running. A sustained processor queue of less than 10 threads per processor is normally acceptable, depending on the workload. There is a single queue for processor time even on computers with multiple processors. Therefore, if a computer has multiple processors, you need to divide this value by the number of processors servicing the workload. |
The User Profile Management (UPM) system provides an easy-to-use User Management and Personalization API that you can use to build Commerce Server applications. The metrics in this category provide information about UPM performance using the performance counters described below.
Table 8-20 User Profile Management Metrics
| Metric | Description and User Action |
|---|---|
|
UPM: Active Connection |
Total number of currently active connections in the connection pool. This counter is for a server, not an instance. |
|
UPM: Active Heap Count |
Total number of currently active heaps in the heap pool. This counter is for a server, not an instance. |
|
UPM: Cache Hit Rate |
Number of cache hits per second for any SQL Server-based properties. This counter is for a server, not an instance. This counter is for a server, not an instance. If your cache miss rate is high in comparison to the cache hit rate, you should increase the size of your cache using the PsObjectCacheSize parameter in the connection string. |
|
UPM: Cache Miss Rate |
Number of cache misses per second for any SQL Server-based properties. This counter is for a server, not an instance. This counter is for a server, not an instance. If your cache miss rate is high in comparison to the cache hit rate, you should increase the size of your cache using the PsObjectCacheSize parameter in the connection string. |
|
UPM: Cache Objects |
Total number of cache objects. This counter is for a server, not an instance. This value should always be equal to or greater than the number of current users on the system. As the rate of this counter against time increases, you need to monitor the disk queue on the back-end data store. |
|
UPM: Create Profile Latency |
Cumulative latency for all profile object creations in one second. This counter is for the server, not an instance. The value of this counter should not be high, because a high value slows user authentication, even when the user already exists on the domain but is not replicated to all domain controllers. |
|
UPM: Delete Profile Latency |
Cumulative latency for all profile object deletions in one second. This counter is for the server, not an instance. |
|
UPM: Get Profile Latency |
Cumulative latency for all profile object retrievals in one second. This counter is for the server, not an instance. The value of this counter should not be high, because a high value slows user authentication, even when the user already exists on the domain but is not replicated to all domain controllers. |
|
UPM: Modify Profile Latency |
Cumulative latency for all profile object updates in one second. This counter is for the server, not an instance. |
|
UPM: Object Creations Per Sec |
Number of profile objects created per second. This counter is for the server, not an instance. |
|
UPM: Object Deletes Per Sec |
Number of profile objects deleted per second. This counter is for the server, not an instance. |
|
UPM: Object Modifies Per Sec |
Number of profile objects modified per second. This counter is for the server, not an instance. |
|
UPM: Object Reads Per Sec |
Number of profile objects retrieved per second. This counter is for the server, not an instance. |
The metrics in the Web Service Metrics category provide information about Web service performance using the performance counters described below.
Table 8-21 Web Service Metrics
| Metric | Description |
|---|---|
|
CGI Requests |
Current number of CGI requests being processed simultaneously by the WWW service. |
|
Current Connections |
Current number of connections established with the HTTP service. A threshold for this counter is dependent on many variables, such as the type of requests (ISAPI, CGI, static HTML, CPU utilization, and so on). |
|
Get Requests |
Current number of HTTP requests using the GET method made to the WWW service. |
|
Head Requests |
Current number of HTTP requests using the HEAD method made to the WWW service. |
|
Logon Attempts Per Sec |
|
|
Post Requests |
Current number of HTTP requests using the POST method made to the WWW service. |
|
Total CGI Requests |
Total number of all CGI requests that have been made since WWW service startup. |
|
Total Connection Attempts (All Instances) |
Total number of attempted connections to the WWW service since service startup. |
|
Total Get Requests |
Total number of HTTP requests that were using the GET method since WWW service startup. |
|
Total Head Requests |
Total number of HTTP requests that were using the HEAD method since WWW service startup. |
|
Total Post Requests |
Total number of HTTP requests that were using the POST method since WWW service startup. |