Seeder and Leech Modes

Although TIBCO MDM is configured in the Seeder mode, it is not always the optimal choice.

You can change the modes using the TIBCO MDM Configurator or by making changes to the ConfigValues.xml file. You must restart all the TIBCO MDM instances after making such changes.

The following information describes and compares Seeder and Leech modes:

  • Seeder: In Seeder mode, TIBCO MDM uses the CacheConfig.xml file to create its own embedded cache node on the same machine that TIBCO MDM is running. This setup is advantageous because the allocated memory is running on the same machine as TIBCO MDM and therefore has substantial performance gain. However, this increases the memory requirements on the host machine considerably.
  • Leech: TIBCO MDM in the leech mode does not create an embedded cache and relies on external cache servers. This setup means that you can spread out the cache over several machines. If TIBCO MDM cannot access any cache nodes it fails and does not function correctly.

If TIBCO MDM instance is a Seeder, the memory used by the TIBCO MDM instance is also the same as the cache configuration. This memory is in addition to the JVM heap assigned.