Physical Memory
Physical memory available on the system should satisfy the TIBCO MDM Heap settings (along with JVM or native thread stack overhead) and accommodate any other processes.
Size the available physical memory accordingly to accommodate the heap settings of the TIBCO MDM Server, memory allocated to the cache server, and any other processes running on the machine.
Before you start multiple instances of TIBCO MDM on the same machine and the cache server, ensure that enough memory is available.
Allocate memory to the distributed cache in the beginning depending on the system memory available. Size the cache according to the memory available to ensure that eviction does not trigger when extensive caching is used in the implementation. See TIBCO ActiveSpaces® Tuning and Configuration for more details.
Preload, an important function, loads the specified number of records into the cache from the database as defined in the TIBCO MDM configuration.
Insufficient memory available on the system for the records to be loaded in cache can trigger an eviction. Memory requirements depend on the attributes defined in the metadata model and the complexity of the data (record hierarchy with relationships). For more details, refer to Preload.