mumc_configyaml>admin_settings>cache>minimum_age

• Parent
  • cache

---

• Description

admin_settings:
  cache:
    minimum_age: integer

• Once the cache is too full for the next entry, minimum_age is used to determine which of the older entries are eligible to be removed from the cache.

• Bigger is not always better:

  • The older an entry is allowed to be, the less entries can be removed from cache when it is full
  • When this happens MUMC will not be able to find any entries to remove and will revert to the fallback_behavior; removing entries until there is enough space in the cache for the newest entry

• Instead of increasing minimum_age it is recommended to first increase the overall cache size

  • A bigger overall cache size means less need to remove entries

• Setting DEBUG: 1 will print the cache statistics to help determine the best cache settings (i.e. size, fallback_behavior, and minimum_age)

• 0-600000 - Minimum cache item's entry age for removal in MILLISECONDS (ms)

---

Example:

minimum_age: 200