Web console statistics

Depending on the view you are using in the web console, you can view different statistics about your configuration. These statistics include the used memory, the top used data grids, and the number of cache entries.

Data grid domain overview
Data grid overview
Data grid details
Server overview
Custom reports: Catalog service domain statistics

Data grid domain overview

Data grid domain overview statistics are displayed on the Monitor > Data Grid Domain Overview page. Click one of the following tabs for more information about the data grid domain:

Used Capacity tab: In the Current Data Grid Used Capacity Distribution chart, a picture of the Total Pool, and the Largest Used Capacity Consumers are displayed. Only the top 25 data grids are displayed. In the Used Capacity Over Time chart, the number of bytes that are consumed by the data grid is displayed.
Average Throughput tab: The 5 Most Active Data Grids by Average Transaction Time in Milliseconds chart contains a list of the top five data caches, organized by the average transaction time. The Average Throughput Over time chart displays the average, maximum, and minimum throughput within the last hour, day, and week.
Average Transaction Time tab: The 5 Slowest Data Grids chart displays data about the slowest data grids. The Average Transaction Time Over Time chart displays the average , maximum, and minimum transaction time within the last hour, day, and week.

Data grid overview

To view statistics for an individual data grid, click Monitor > Data Grid Overview > data_grid_name.

Current summary over last 30 seconds: Displays the current number of cache entries, average transaction time, average throughput, and cache hit rate for the selected data grid.
Used Capacity tab: The Current summary over last 30 seconds chart displays the number of cache entries and used capacity in bytes over a specified time range.
Cache Usage tab: The Cache Usage chart helps to visualize the number of successful queries to the cache, and displays cache attempts, cache hits, and the cache hit rate over a specified time range.
Average Throughput tab: The Average Throughput vs. Average Transaction Time chart displays the transaction time and throughput over a specified time range.

Data grid details

Data grid statistics are displayed on the Monitor > Data Grid Details page. You can look at data for a selected grid and the maps that are within that grid.

Current summary over last 30 seconds: Displays the current used capacity, number of cache entries, average throughput, and average transaction time for the selected data grid.
Current eXtreme Scale Object Grid Map Used Capacity Distribution: View a total pool, which includes the capacity by zone and the total capacity in each zone. Only the top 25 ObjectGrid maps are displayed. You can also view the largest used capacity consumers by each map.
Current Zone Used Capacity Distribution: View a total pool, which includes the total pool and the top used capacity consumers in the zone of the selected data grid. You can also view the largest used capacity consumers by each zone.

Map statistics:
Current summary over last 30 seconds: Displays the current used capacity, number of cache entries, average throughput, and average transaction time for the selected map.
Current Partition Used Capacity Distribution: View a partition, which includes the total pool and the top used capacity consumers. Only the top 25 partitions are displayed. You can also view the largest used capacity consumers by each partition.

Server overview

Server statistics are displayed on the Monitor > Server Overview page.

Current Server Used Memory Distribution: This chart is composed of two views. Total Pool displays the current amount of used (real) memory in the server run time. Largest Used memory Consumers breaks down the used memory by server; however only the top 25 servers that are using the most memory are displayed.
Total Memory Over Time: Displays the real memory usage in the server run time.
Used Memory Over Time: Displays the amount of used memory in the server run time.

Custom reports: Catalog service domain statistics

You can view catalog service domain statistics by creating a custom report. Click Monitor > Custom Reports.

Average Transaction Time (ms): Displays the average time required to complete a transaction in this domain.
Average Transaction Throughput (trans/sec): Displays the average number of transactions per second in this domain.
Maximum Transaction Time (ms): Displays the time spent by the most time-consuming transaction in this domain.
Minimum Transaction Time (ms): Displays the time spent by the least time-consuming transaction in this domain.
Total Transaction Time (ms): Displays total time spent on transactions in this domain, since the time the domain was initialized.

Custom reports: Container server statistics

You can view container server statistics by creating a custom report. Click Monitor > Custom Reports.

Average Transaction Time (ms): Displays the average time required to complete a transaction for this catalog server.
Average Transaction Throughput (trans/sec): Displays the average number of transactions per second for this catalog server.
Maximum Transaction Time (ms): Displays the time spent by the most time-consuming transaction for this catalog server.
Minimum Transaction Time (ms): Displays the time spent by the least time-consuming transaction for this catalog server.
Total Transaction Time (ms): Displays total time spent on transactions for this catalog server, since the time for this catalog server was initialized.
Total Entries in Cache: Displays the current number of objects cached in the grids overseen by this catalog server.
Hit rate (percentage): Displays the hit rate (hit ratio) for the selected data grid. A high hit rate is desirable. The hit rate indicates how well the grid is helping to avoid accessing the persistent store.
Used Bytes: Displays memory consumption by this map. The used bytes statistics are accurate only when you are using simple objects or the COPY_TO_BYTES copy mode.
Minimum Used Bytes: Displays the low point in memory consumption by this catalog service and its maps. The used bytes statistics are accurate only when you are using simple objects or the COPY_TO_BYTES copy mode.
Maximum Used Bytes: Displays the high point in memory consumption by this catalog service and its maps. The used bytes statistics are accurate only when you are using simple objects or the COPY_TO_BYTES copy mode.
Total Number of Hits: Displays the total number of times the requested data was found in the map, avoiding the need to access persistent store.
Total Number of Gets: Displays the total number of get operations on the map. The total determines both hits and misses that the map made to obtain data.
Free Heap (MB): Displays the actual amount of heap available to the JVM being used by the catalog server.
Total Heap: Displays the amount of heap available to the JVM being used by this catalog server.
Number of Available Processors: Displays the number of processors that are available to this catalog service and its maps. For the highest stability, run your servers at 60% processor loading and JVM heaps at 60% heap loading. Spikes can then drive the processor usage to 80–90%, but do not regularly run your servers higher than these levels
Maximum Heap Size (MB): Displays the maximum amount of heap available to the JVM being used by this catalog server.
Used Memory: Displays the used memory in the JVM being used by this catalog server.

Custom reports: Data grid statistics

You can view data grid statistics by creating a custom report. Click Monitor > Custom Reports.

Average Transaction Time (ms): Displays the average time required to complete transactions involving this grid.
Average Transaction Throughput (trans/sec): Displays the average number of transactions per second completed by this grid.
Maximum Transaction Time (ms): Displays the time spent by the most time-consuming transaction completed by this grid.
Minimum Transaction time (ms): Displays the time spent by the least time-consuming transaction completed by this grid.
Total Transaction Time (ms): Displays the total amount of transaction processing time for this grid.

Custom reports: Map statistics

You can view map statistics by creating a custom report. Click Monitor > Custom Reports.

Total Entries in Cache: Displays the current number of objects cached in this map.
Hit Rate (percentage): Displays the hit rate (hit ratio) for the selected map. A high hit rate is desirable. The hit rate indicates how well the map is helping to avoid accessing the persistent store.
Used Bytes: Displays memory consumption by this map. The used bytes statistics are accurate only when you are using simple objects or the COPY_TO_BYTES copy mode.
Minimum Used Bytes: Displays the minimum consumption (in Bytes) for this map. The used bytes statistics are accurate only when you are using simple objects or the COPY_TO_BYTES copy mode.
Maximum Used Bytes: Displays the maximum consumption (in Bytes) for this map. The used bytes statistics are accurate only when you are using simple objects or the COPY_TO_BYTES copy mode.
Total Number of Hits: Displays the total number of times the requested data was found in the map, avoiding the need to access persistent store.
Total Number of Gets: Displays the total number of times the map had to access the persistent store to obtain data.
Free Heap (MB): Displays the current amount of heap available to this map, in the JVM being used by the catalog server.
Total Heap (MB): Displays the total amount of heap available to this map, in the JVM being used by the catalog server. For the highest stability, run your servers at 60% processor loading and JVM heaps at 60% heap loading. Spikes can then drive the processor usage to 80–90%, but do not regularly run your servers higher than these levels
Number of Available Processors: Displays the number of processors available to this map. For the highest stability, run your servers at 60% processor loading and JVM heaps at 60% heap loading. Spikes can then drive the processor usage to 80–90%, but do not regularly run your servers higher than these levels
Maximum Heap Size (MB): Displays the maximum amount of heap available to this map, in the JVM being used by the catalog server.
Used Memory (MB): Displays the used amount of memory in this map.