|
Measures reported by IgniteCaGrouTest
Caches within a single cache group share various internal structures such as partitions maps, thus boosting topology events processing and decreasing overall memory usage. Note that from the API standpoint, there is no difference whether a cache is a part of a group or not.
Cache groups help in managing the overheads and if there are very large number of caches, the overall time required in deploying and managing the caches will be significantly reduced if using cache groups.
Since the data partitioning is done at cache group level, proper grouping and partitioning within the group is essential to better cache performance. That's the reason it is important to monitor the cache groups, so that any issues can be addressed in timely manner and application performance is not impacted.
This test monitors the cache groups and gathers key statistics around the usage of cache groups and partitions which can help administrators spot any current or future issues and take corrective actions.
Outputs of the test: One set of results for each Apache Ignite Server
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| partitions |
Indicates the total number of partitions in cache group. |
Number |
The number of partitions should be optimal based on the performance required and data to be accessed.
|
| clusterMovingPartition |
Indicates the total number of partitions for given cache group in the entire cluster with state MOVING. |
Number |
|
| clusterOwningPartition |
Indicates the total number of partitions for given cache group in the entire cluster with state OWNING. |
Number |
|
| indBuildCntPartitionLeft |
Indicates the maximum number of partition copies for all partitions of this cache group. |
Number |
|
| localNodeMovingPartition |
Indicates the count of nodes with MOVING state for given cache group located on a given node. |
Number |
|
| localNodeOwningPartition |
Indicates the count of nodes with OWNING state for given cache group located on a given node. |
Number |
|
| localNodeRentingEntries |
Indicates the number of entries which remains to evict RENTING partitions located on same node for given cache group. |
Number |
|
| localNodeRentngPartition |
Indicates the count of nodes with RENTING state for given cache group located on a given node. |
Number |
|
| maxNumbOfPartitionCopie |
Indicates the maximum number of partition copies for all partitions of this partition group. |
Number |
A very large number of copies can occupy a lot of storage unnecessarily.
|
| minNumbOfPartitionCopie |
Indicates the minimum number of partition copies for all partitions of this partition group. |
Number |
There should be a minimum number of copies to be held in case if there is failure.
|
| sparseStorageSize |
Indicates the storage space allocated for the cache group adjusted for sparsity. |
MB |
|
| storageSize |
Indicates the storage space allocated for entire cache group. |
MB |
Storage allocated should be as per requirement and administrators need to keep an eye on required and used storage so as to use storage optimally.
|
| totalAllocatedPages |
Indicates the total number of memory pages allocated for given cache group. |
Number |
|
| totalAllocatedSize |
Indicates the total size of memory allocated for given cache group. |
MB |
|
|