Persistence Tuning

Consider using separate drives for data files and replications logs. GridGain actively writes to both the data and log files.

TODO doc team how to configure this

GridGain periodically starts the checkpointing process that syncs dirty pages from memory to disk.

If dirty pages are allocated faster than they are written to disk, write throttling may occur. If you see a saw-like picture in write load and messages like "Throttling is applied to page modifications", consider:

Note that the performance of Ignite Native Persistence may drop after several hours of intensive write load due to the nature of how SSDs are designed and operate. Consider buying fast production-level SSDs to keep the performance high or switch to non-volatile memory devices.

Performance of random writes on a 50% filled disk is much better than on a 90% filled disk because of the SSDs over-provisioning.

Consider buying SSDs with higher over-provisioning rates and make sure the manufacturer provides the tools to adjust it.

GridGain was designed to work on non-rotating devices. It’s not recommended to deploy GridGain on HDD due to possible performance issues.

GridGain utilizes multi version data model, which means multiple copies of the same row exist in the storage. This can quickly exhaust the storage capactity under specific scenarios. Make sure you adjust GC watermark to avoid uncontrollable history growth.

TODO doc team link to low watermark configuration