Social object cache
This cache is enabled by default. It caches data that is served by IBM Connections. It can have a larger effect on performance than the data source cache.Data source cache
This cache is enabled by default. It caches the HTTP response from IBM Connections.Social list cache
This cache is disabled by default. It caches the social list markup. Of the three cache layers that are listed here, the social list cache can have the strongest effect on performance.
For more information, see the following topics.
Social object cacheParent topic: Administering social lists
The social object cache layer caches Java objects that are used to build the social objects that are displayed in social list results portlets. For requested data, social rendering first looks in the social object cache layer. The social object cache contains Java objects that are used to fill the result lists for the social list result portlets. Therefore, it can have a larger effect on performance than the data source cache.
Data source cache
If social rendering does not find the requested social objects in the social object cache layer, it looks in the DataSource
cache layer. This cache layer caches the HTTP response from IBM
Connections. The HTTP response body contains an IBM
Connections feed. A cache hit in this layer avoids network traffic. However, in contrast to the social object cache layer, social rendering must parse the feeds again to build the corresponding social objects.
Social list cache
The social list cache can help reduce processor consumption when the portal repeatedly renders the same social lists.