3.16.1. Portal caches

eXo Platform provides a list of Portal caches, including:

These Portal caches can be overridden in the following files. See Configuration overview for how-to.

# Portal Cache Configuration - MOP session Manager
#  - Standalone (live time in seconds)
exo.cache.portal.mop.maxsize=5000
exo.cache.portal.mop.livetime=600
#  - Cluster (expiration in milliseconds)
exo.cache.portal.mop.maxnodes=5000
exo.cache.portal.mop.expiration=600000

# Portal Cache Configuration - Navigation Service
#  - Standalone (live time in seconds)
exo.cache.portal.navigation.maxsize=5000
exo.cache.portal.navigation.livetime=600
#  - Cluster (expiration in milliseconds)
exo.cache.portal.navigation.maxnodes=5000
exo.cache.portal.navigation.expiration=600000

# Portal Cache Configuration - Description Service
#  - Standalone (live time in seconds)
exo.cache.portal.description.maxsize=5000
exo.cache.portal.description.livetime=600
#  - Cluster (expiration in milliseconds)
exo.cache.portal.description.maxnodes=5000
exo.cache.portal.description.expiration=600000

# Portal Cache Configuration - Page Service
#  - Standalone (live time in seconds)
exo.cache.portal.page.maxsize=5000
exo.cache.portal.page.livetime=600
#  - Cluster (expiration in milliseconds)
exo.cache.portal.page.maxnodes=5000
exo.cache.portal.page.expiration=600000

# Portal Cache Configuration - Template Service
#  - Standalone (live time in seconds)
exo.cache.portal.TemplateService.capacity=3000
exo.cache.portal.TemplateService.liveTime=3600

# Portal Cache Configuration - ResourceBundleData
#  - Standalone (live time in seconds)
exo.cache.portal.ResourceBundleData.capacity=3000
exo.cache.portal.ResourceBundleData.liveTime=-1

The specific configuration of Portal caches can be found in the files:

i. For MOPSessionManager, NavigationService, DescriptionService, PageService:

ii. For TemplateService and ResourceBundle:

MOPCache

The MOPCache caches all model objects of the portal (MOP), such as sites, pages and preferences. When the cached MOP objects are called, they will be directly retrieved from cache rather than the database.

NavigationCache

The NavigationCache caches data of navigation. When the cached navigation is accessed, it will be retrieved from cache rather than the database.

DescriptionCache

The DescriptionCache caches a pair of name-description. Accordingly, the cached pair of name-description will be taken directly from cache rather than the database.

PageCache

The PageCache caches data of a page when one user visits it for the first time. When the cached page is visited, it will be loaded from cache rather than the database.

TemplateCache

The TemplateCache caches all Groovy templates of the portal by its template path and ResourceResolver. When the cached template is called, it will be loaded from cache rather than the database or the file system.

ResourceBundleCache

The ResourceBundleCache caches all resource bundles by name and locale. When the cached resource bundle is called, it will be directly loaded from cache rather than the database or the file system.

Copyright ©. All rights reserved. eXo Platform SAS
blog comments powered byDisqus