Preload
Default preload configuration preloads most of the metadata and record data. You do not need to change this for small and medium sized systems, for example, for a few 100,000 records.
Regardless of the record count, you should always preload CATALOG, ENTERPRISE.
Compute the requirement memory for preloading all the record data and if memory is sufficient, load all the record data by specifying RECORD, RECORDMAXMODVERSION, PRODUCTKEY, SYNCLOG, and SYNCRECORD.
However, if you have insufficient memory to accommodate all objects, consider preloading in the following priority:
PRODUCTKEY
RECORDMAXMODVERSION
SYNCLOG (if synchronization performance needs to be improved)
RECORD
SYNCRECORD
Do not set up preload to a large number of records without sufficient cache because the records are evicted as the cache fills up. Using the JMX console, check the record count in cache to ascertain whether the records are being evicted. If the record count in cache is less than the number of records preloaded, stop the preload.
Import and export performance is better if data is preloaded. Database Loader does not use cached data and is not impacted.
Preload automatically preloads all the children repository metadata and records even if only the parent repository is specified for preload.
For every record, approximately three entries are created in the RECORD and RECORDMAXMODVERSION caches while two entries are created in the PRODUCTKEY repository.