Configuring the ledger import cache
Use the Ledger Import Cache to set the memory allocation for each cache. This is specified in terms of the maximum number of records that can be held in the cache at one time.
During an import, the caching process analyzes an input payload and calculates the memory cache required, based on the number and type of records being imported. For example, an import payload with fewer records but many fields may take much longer to process than an import payload with lots of records but a very simple set of fields. The process only allocates what is required for each individual import.
After analysis, the records are loaded into the cache. In most cases, the memory allocation will be much smaller than the maximum specified in the settings.
It is possible, although unlikely, that the maximum cache allocation will be exceeded. In such cases, records in the cache will be read first before the previous read process is reverted to.
If you are running an extremely large import in excess of 200,000 different static data records, and this is run on a frequent basis then there may be a case for increasing the maximum cache settings but this is an exceptional circumstance.
Before altering the cache settings, consider your memory availability.
Configure the ledger import cache settings.