Dynamic Cache Templates attributes
The attributes provide dynamic cache template information.
The Dynamic Cache Templates attribute group provides information about the cache template data.
A cache template is an object type defined by a cache policy specified in the WebSphere® Application Server cachespec.xml file. A cache policy specifies the cache rules indicating what is cached, the invalidation, timeout conditions, and other data. The attributes within this group are used to build the Cache Analysis workspace.
- The attributes within this attribute group contain zeros for performance data if your site has set configuration value Resource Data Collection Method to On Demand (for on-demand sampling) and if you have not yet run applications that generate performance data. To report performance data in these attributes after installing and configuring the data collector, use the WebSphere administrative console to set the appropriate PMI instrumentation level.
- The monitoring agent is set by default to provide on-demand sampling; thus the attributes within this attribute group initially contain zeros until you select the workspace and select it again later. Each time you select the workspace, these attributes are updated with the latest data.
Cache Instance Name The cache instance name.
Cache Instance Type The cache instance type.
Cache Miss Rate (per sec) The rate (per second) of requests for this cacheable object type that were not found in the cache during the sampling interval. The valid format is a decimal (formatted to three decimal places).
Cache Misses The number of requests for this cacheable object type that were not found in the cache (in memory, on disk or on other cooperating caches). This would have caused the underlying servlet or command to be executed in order to obtain the results. The valid format is a positive integer.
Cache Object Type The name of the object type specified in the cache policy of the cache spec XML file. The valid format is an alphanumeric string, with a maximum of 256 characters.
Client Request Rate (per sec) The request rate (per second) for this cacheable object type made by clients directly accessing this application server. The valid format is a decimal (formatted to three decimal places).
Client Requests The number of requests for this cacheable object type made by clients directly accessing this application server. The valid format is a positive integer.
Cluster Request Rate (per sec) The request rate (per second) for this cacheable object type made by cooperating caches in this cluster. The valid format is a decimal (formatted to three decimal places).
Cluster Requests The number of requests for this cacheable object type made by cooperating caches in this cluster. The valid format is a positive integer.
Current Cache Size The current number of entries for this cacheable object type present in the dynamic cache. The valid format is a positive integer.
Disk Hit Rate (per sec) The rate (per second) of the requests for this cacheable object type served from disk during the sampling interval. The valid format is a decimal (formatted to three decimal places).
Disk Hits The number of requests for this cacheable object type that were served from disk. This applies only when the disk offload is turned on for the dynamic cache. The valid format is a positive integer.
Explicit Disk Invalidations Rate (per sec) The rate at which the entries of this cacheable object type were removed from disk due to explicit invalidations issued by the clients. The valid format is a decimal (formatted to three decimal places).
Explicit Disk Invalidations The number of entries of this cacheable object type that were removed from disk due to explicit invalidations issued by the clients (directly accessing the application server and by remote JVMs in the cluster). The valid format is a positive integer.
Explicit Local Invalidation Rate (per sec) The rate at which the explicit invalidations were received for this cacheable object type from clients accessing the application server directly, either programmatically or by a cache policy. The valid format is a decimal (formatted to three decimal places).
Explicit Local Invalidations The number of explicit invalidations received for this cacheable object type from clients accessing the application server directly, either programmatically or by a cache policy. The valid format is a positive integer.
Explicit Memory Invalidation Rate (per sec) The rate at which the entries of this cacheable object type were removed from memory due to explicit invalidations issued by the clients. The valid format is a decimal (formatted to three decimal places).
Explicit Memory Invalidations The number of entries of this cacheable object type that were removed from memory due to explicit invalidations issued by the clients (directly accessing the application server and by remote JVMs in the cluster). The valid format is a positive integer.
Explicit Remote Invalidation Rate (per sec) The rate at which explicit invalidations were received for this cacheable object type from cooperating JVMs in the cluster. The valid format is a decimal (formatted to three decimal places).
Explicit Remote Invalidations The number of explicit invalidations received for this cacheable object type from cooperating JVMs in the cluster. The valid format is a positive integer.
Instrumentation Level The PMI instrumentation level set for collecting dynamic cache data. For WebSphere Version 6 or later, the valid values are None, Basic, Extended, All, Custom. Blank if no instrumentation level is set.
Interval (sec) The length (in seconds) of the sampling interval. The valid format is a positive integer.
Least Recently Used Invalidation Rate (per sec) The rate (per second) at which entries of this cacheable object type were evicted from memory by a least-recently used algorithm. The valid format is a decimal (formatted to three decimal places).
Least Recently Used Invalidations The number of entries of this cacheable object type that were evicted from memory by a least-recently-used algorithm. This happens when the in-memory cache becomes full and subsequent requests for new entries must be accommodated. The entries removed from memory are passivated to disk if disk overflow is enabled. If this number is high, consider increasing the in-memory cache size. The valid format is a positive integer.
Memory Hit Rate (per sec) The rate (per second) of the requests for this cacheable object type served from memory during the sampling interval. The valid format is a decimal (formatted to three decimal places).
Memory Hits The number of requests for this cacheable object type served from memory. The valid format is a positive integer.
Node Name The name of the system on which the server is running. The valid format is an alphanumeric string, with a maximum of 128 characters.
Origin Node The name of the server subnode. The valid format is an alphanumeric string, with a maximum of 128 characters.
Remote Cache Entries Received The number of entries received from cooperating dynamic caches in this cluster. The valid format is a positive integer.
Remote Cache Entry Receive Rate (per sec) The rate (per second) of entries received from cooperating dynamic caches in this cluster for the sampling interval. The valid format is a decimal (formatted to three decimal places).
Remote Hit Rate (per sec) The rate (per second) of the requests for this cacheable object type served from other JVMs in the cluster during the sampling interval. The valid format is a decimal (formatted to three decimal places).
Remote Hits The requests for this cacheable object type served from other JVMs in the cluster. The valid format is a positive integer.
Sample Date and Time The date and time the monitoring agent collected the data. The valid format is a 12-character timestamp. For the STR and SCAN functions, the format is MM/DD/YY HH:MM:SS; the following table shows the values contained in this character string.
| Character String | Meaning |
|---|---|
| MM | Month |
| DD | Day |
| YY | Year |
| HH | Hour |
| MM | Minute |
| SS | Second |
Example: 09/13/06 18:32:03 indicates the data was collected on September 13 2006, at 18:32:03.
This attribute was designed for logging and reporting data-collection times rather than for creating situations. To specify a time and date for comparison and testing, use attributes from the Universal Time or Local Time groups.
Server Name The name of the WebSphere Application Server. The valid format is an alphanumeric string, with a maximum of 256 characters.
Set Instrumentation Level Type Indicates the WebSphere resource category, which is used by the agent to modify the Instrumentation Level for transaction data collection.
Summary of Cache Templates Whether this row is a summary row of statistical totals collected for all the cache object types. The valid values are No and Yes.
Template Row Number The number of the row in the report that displays in the workspace, which is associated with a bar in the Ten Worst Hits Rate bar chart. The valid format is an integer.
Timeout Invalidation Rate (per sec) The rate (per second) at which entries are removed from the cache (memory or disk) because their timeout has expired. The valid format is a decimal (formatted to three decimal places).
Timeout Invalidations The number of entries of this cacheable object type that were removed from memory or disk because their timeout (as specified in the cache spec XML file) has expired. The valid format is a positive integer.
Total Explicit Invalidation Rate (per sec) The rate at which invalidations were issued for entries for this cacheable object type explicitly by the clients. The valid format is a decimal (formatted to three decimal places).
Total Explicit Invalidations The number of invalidations issued for entries of this cacheable object type explicitly by the clients (directly accessing the application server and by remote JVMs in this cluster). The valid format is a positive integer.
Total Hit Rate (per sec) The total hit rate per second. The valid format is a decimal (formatted to three decimal places).