Cache Customization - Legacy
Legacy cache support is based on OSCache. This support is deprecated and will be removed at some point in the future. Recommend using the current support documented in New Cache Management Options.
OSCache Customization
- For normal usage, properties do not need to be changed.
- Properties for the cache behavior are specified in .../WEB-INF/classes/oscache.properties.
The properties file no longer ships with Confluence, but can be created. The default without a specific property file is:
.../WEB-INF/classes/oscache.propertiescache.memory=true cache.capacity=1000
- The capacity property equal to 1000 means that 1000 distinct renderings of the cache macro will be cached. Additional distinct renderings will replace previously cached entries. You should increase the capacity only if you used the cache macro in many places (over 1000) that are accessed regularly and the extra JVM memory used will be acceptable.
- If your system is memory constrained, consider adding a configuration file to restrict memory usage by setting cache.capacity=100 or cache.capacity=250
- The rendered html is cached, so normally that may be a few KB per entryÂ
Confluence®, Jira®, Atlassian Bamboo®, Bitbucket®, Fisheye®, and Atlassian Crucible® are registered trademarks of Atlassian®
Copyright © 2005 - 2024 Appfire | All rights reserved. Appfire™, the 'Apps for makers™' slogan and Bob Swift Atlassian Apps™ are all trademarks of Appfire Technologies, LLC.