Ignite Persistence Test

Ignite Persistence, or Native Persistence, is a set of features designed to provide persistent storage. When it is enabled, Ignite always stores all the data on disk, and loads as much data as it can into RAM for processing.

Persistence ensures that all the data in the RAM is backed-up and can be used if the cache fails or for distribution to downstream systems. That is the reason it is important to regularly monitor persistence, so that administrator have full idea if there is any issue and can re-mediate in timely manner.

This tests monitors the persistence storage and collects key metrics like- Memory allocated size, Write-Ahead Logging archive segments, page reads etc, which can help administrator make informed decisions about storage's health.

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



Test period

How often should the test be executed.


Enter the IP address of the Apache Ignite cluster.


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 Unit


Pages read

Indicates the number of pages read since last restart.



Pages replaced

Indicates the number of pages replaced since last restart.


Too many pages replaced may not be ideal for performance.

Pages written

Indicates the number of pages written since last restart.



Dirty pages

Indicates the number of pages in memory that have been changed but not yet synchronized to disk. Those will be written to disk during next checkpoint.


If the number of dirty pages is too high, it is too risky if the cache goes down there will be high data loss.

Used checkpoint buffer page

Indicates the total number of checkpoint buffer pages used since last restart.



Off-heap size

Indicates the total memory in MB allocated in off-heap cache.


Off-heap storage doesn't have memory management so it is fast, but the allocation should be optimal.

Off-heap used size

Indicates the total memory in MB used in off-heap cache.



Checkpoint buffer size

Indicates the total size of checkpoint buffer.


A low value is desired for this measure.

Used checkpoint buffer size

Indicates the total size of checkpoint buffer which is currently in use.


You need to take an action if the used checkpoint reaches near the total size of checkpoint buffer.

Last checkpoint duration

Indicates the total time it took to create the last checkpoint.



Total allocated size

Indicates the size of the space allocated on disk for the entire data storage (in MB). Note that when Native persistence is disabled, this metric shows the total size of the allocated space in RAM.


This metrics should be actively monitored and administrators should ensure that there is always enough memory available to support the applications and users.

Write-Ahead Logging archive segments

Indicates the number of WAL segments in the archive.


The write ahead logs should be actively manages and cleared when not required.

Write-Ahead Logging buffer poll spins rate

Indicates the WAL buffer poll spins number over the last time interval.



Write-Ahead Logging fsync time average

Indicates the total duration of write-ahead logging fsync.



Write-Ahead Logging log rate

Indicate the average number of WAL records per second written during the last time interval

Records /sec


Write-Ahead Logging total size

Indicates the total size of the WAL files in MB, including the WAL archive files.


The write ahead log size should be optimal for the performance of the system.

Write-Ahead Logging write rate

Indicates the average number of MB per second written during the last time interval.


Ideally this number should be high, but if the write rate is going down over ht measurements then it may be a matter of concern.