Summary: A configuration schema that defines how a space should persist its in-memory data to disk-based storage (either RDBMS when using the JDBC SA).
OverviewThe persistent space running with the JDBC SA options described below:
Defining Cache SizeWhen a persistent space (using the JDBC SA) is using LRU cache policy and the space has been restarted, it loads data from the underlying durable data source (RDBMS) before being available for clients to access. The default behavior is to load data up to 50% of the <cache_size> value. When the <memory_usage> is true (evicting data from the space based on free heap size), is it recommended to have a large value for the <cache_size> property. This instructs the space engine to ignore the amount of Entries inside the space when launching the eviction mechanism. This ensures that the eviction is based only on heap size free memory. The combination of the above (large <cache_size> and space restart) may lead to out of memory problems. To avoid this, configure the space-config.engine.initial_load to have a low value (5 below means 5% of the <cache_size> – default is 50%): XPATH property: space-config.engine.initial_load=5 The <initial_load_class> property specifies which class to load. For example: space-config.engine.initial_load_class=com.myCompany.myEntry |
![]() |
GigaSpaces.com - Legal Notice - 3rd Party Licenses - Site Map - API Docs - Forum - Downloads - Blog - White Papers - Contact Tech Writing - Gen. by Atlassian Confluence |