Ignite Data Region Test

Ignite uses the concept of data regions to control the amount of RAM available to a cache or a group of caches. A data region is a logical extendable area in RAM in which cached data resides. You can control the initial size of the region and the maximum size it can occupy. In addition to the size, data regions control persistence settings for caches. By default, there is one data region that can take up to 20% of RAM available to the node, and all caches created are placed in that region; but as many regions can be created as required.

The data region configurations dictate how much memory is used for caching. It is important to monitor the data regions so as to be updated of current capacity on the node that caches are consuming and if there is any scope for extension.

This test monitors the Ignite nodes data regions and collects key statistics which allow administrators to take actions.

Target of the test : Apache Ignite Server

Agent deploying the test : An internal or external agent

Outputs of the test : One set of results for each Apache Ignite Server

Configurable parameters for the test

Parameter	Description
Test period	How often should the test be executed.
Host	Enter the IP address of the Apache Ignite cluster.
Port	Enter the port number on which JMX connector listens to incoming connections requests.
JMX Remote Port	In this text box, enter the name of a virtual warehouse that needs to be monitored. The JMX connector listens on 8686 by default. If it listens on different port in your environment then specify the same.
JMX User	Specify the credentials of the user who is authorized to use JMX.
JMX Password	Specify the password for the authorized user.
Confirm Password	Confirm the password by retyping it here.

Measurements made by the test

Measurement	Description	Measurement Unit	Interpretation
Pages fill factor	Indicates the average size of data in pages as a ratio of the page size. When Native persistence is enabled, this metric is applicable only to the persistent storage (i.e. pages on disk).	Number	If the page fill factor is too high there will be no space available in the page to allocate new memory, and new page will have to be allocated which will make the process slow.
Total used pages	Indicates the number of data pages that are currently in use. When Native persistence is enabled, this metric is applicable only to the persistent storage (i.e. pages on disk).	Number
Physical memory pages	Indicates the total number of pages allocated in RAM.	Number	The optimal number should be allocated for best performance.
Physical memory size	Indicates the size of memory allocated in RAM in MB.	MB	Total size of physical memory should be allocated to provide best performance.
Total allocated size	Indicates the size of the space allocated for this data region (in MB). Note that when Native persistence is disabled, this metric shows the total size of the allocated space in RAM.	MB
Page’s replacement rate	Indicates the rate at which pages in memory are replaced with pages from persistent storage (pages per second).	Pages/Sec	Higher the rate, better the performance.
Allocation rate	Indicates the average memory allocation rate across the nodes.	Pages/Sec
Eviction rate	Indicates the average memory eviction rate across the nodes.	Pages/Sec