[JS2-1325] Preferences Caching Performance Improvements

• Type: Improvement
• Status: Resolved
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.3.0
• Fix Version/s: 2.3.0
• Component/s: Portlet Entities and Preferences
• Assignee: David Sean Taylor
• Reporter: David Sean Taylor
• Due: 15/May/15
• Created: 01/May/15 18:57
• Updated: 12/Jun/15 22:31
• Resolved: 12/Jun/15 22:31

Description

The Preferences Model uses a PUBLIC cache in the form of the Jetspeed cache in order to store default preferences. (This works well except for the fact that Ehcache does not support negative caching and therefore database calls which have no results end up falling through the cache cycle.) The Preferences Model however does not leverage PRIVATE caching (users session) to store user specific preferences and therefore the preferences are pulled back as required resulting in some of the large volume of requests

Improvement: preloading these preferences in the PRIVATE cache using a single call when the user hits the page for the first time.