eXo Platform provides 3 Wiki caches, including:
You can change these Social caches that are handled by PageRenderingCacheService in the following files. See Configuration overview for how-to.
# == WIKI Caches Configuration == #
# Wiki Cache Configuration - Spaces
# - Standalone (time to live in seconds)
The specific configuration of each Wiki cache can be found in:
The RenderingCache caches content of visited wiki pages. When any users visit the cached wiki pages, their content will be retrieved from cache rather than the database.
The RenderingCache is updated when a wiki page is removed or modified.
The RenderingCache size equals to the number of wiki pages in cache.
The size of a wiki page is unlimited, so the maximum heap size consumed by the cache is unlimited too. However, most of wiki pages are often less than 100KB. Therefore, the maximum heap size equals to the cache size multiplied by 100KB.
The UuidCache caches Uuid of nodes that stores the visited wiki pages. When any users visit these wiki pages, Wiki gets the nodes by UUID in cache that is much faster than query in the database.
The UuidCache is updated when the wiki page is removed.
The UuidCache size equals to the number of wiki pages in cache.
Every Uuid has the length of 32 bytes, so the maximum heap size equals to the cache size multiplied by 32 bytes.
The AttachmentCountCache caches the number of attachments of the visited wiki pages. When the visited wiki pages are called, the number of page attachments will be retrieved from cache rather than the database.
The AttachmentCountCache is updated when the wiki page is removed/modified or when its attachment is added/removed.
The AttachmentCountCache size equals to the number of wiki pages in cache.
The maximum heap size equals to the cache size multiplied by 4 bytes ("4" - size of Integer).