| Administering the Platform / In-Memory Caching | |
In-memory caching reduces the number of trips the application makes to its database by holding often-requested data in memory. When you configure cache servers, you give each server the list of all cache server machines. For example, you might edit the list of cache server machines when you're adding or removing servers.
For information on adding and removing cache servers, see Managing Cache Servers. For information on installing cache servers, see Setting Up a Cache Server.
The Caches page in the Admin Console lists the application's caches and provides information on how well they're being used. This information is for use in troubleshooting if you need to call Jive support.
You need to register the cache server(s) in the Cache Servers box of the Caches Admin Console page. If you have more than one cache server, such as with a high-availability configuration, they must all be listed a comma separated list of either IP addresses or domain names, but be consistent with the format (use IP addresses or domain names, but don't combine them) and order you use. For more on this and setting up cache servers for high-availability, see Configuring the Cache Servers for High-Availability.
For more information about adding, removing, and moving cache servers, see Managing Cache Servers.
When requested by Jive Support, you can provide information about caches using the Cache Performance Summary table on the Caches page in the Admin Console. There, you'll find a list the individual kinds of data cached. Many represent content, such as blog posts and documents. Others represent other data that can be performance-expensive to retrieve from the database.
| Column Name | Description |
|---|---|
| Cache Name | You can click the cache name to view advanced statistics about the cache. You might use these statistics when working with the support team to resolve cache-related issues. General information about the advanced statistics is provided below. |
| Objects | Generally speaking, each object in the cache represents a different instance of the item. For example, if the Blog cache has 22 objects in it, it means that 22 of the community's blogs are represented there. |
| Hits / Misses | A cache hit is recorded when a query to the cache for the item actually finds it in the cache; a cache miss is when the item isn't found in the cache and the query much go to the database instead. As you might imagine, a higher ratio of hits to misses is more desirable because it means that requests are finding success in the cache, making performance from the user's perspective better. |
| Effectiveness | The effectiveness number -- a percentage -- is a good single indicator of how well a particular cache is serving your application. When a cache is being cleared often (as might happen if memory constraints are being reached), the ratio of cache hits to misses will be lower. |
| Clear Cache Check Box | When you're asked to clear a cache, select its check box, then click the Clear Selected button at the bottom of the cache list table. |