[jira] [Comment Edited] (JS2-1324) Security Cache Performance Improvements

    [ https://issues.apache.org/jira/browse/JS2-1324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14532124#comment-14532124 ] 

Randy Watler edited comment on JS2-1324 at 5/7/15 6:55 AM:
-----------------------------------------------------------

Checkpoint commit with initial JetspeedSecurityPersistenceManager, (JSPM), cache integration.

New security cache configuration properties, (jetspeed.properties):

{code}
#-------------------------------------------------------------------------
# S E C U R I T Y   P E R S I S T E N C E   C A C H E
#-------------------------------------------------------------------------
# jetspeed security persistence manager cache size:
#org.apache.jetspeed.ehcache.jspm.maxelements=128
# jetspeed security persistence manager cache element expiration in seconds, (infinite = 0):
#org.apache.jetspeed.ehcache.jspm.element.ttl=150
{code}

To Do:

# Review JSPM cache performance.
# Add distributed JSPM cache unit tests.


was (Author: rwatler):
Checkpoint commit with initial JetspeedSecurityPersistenceManager, (JSPM), cache integration.

New security cache configuration properties, (jetspeed.properties):

{code}
#-------------------------------------------------------------------------
# S E C U R I T Y   P E R S I S T E N C E   C A C H E
#-------------------------------------------------------------------------
# jetspeed security persistence manager cache size:
#org.apache.jetspeed.ehcache.jspm.maxelements=128
# jetspeed security persistence manager cache element expiration in seconds, (infinite = 0):
#org.apache.jetspeed.ehcache.jspm.element.ttl=150
{code}

> Security Cache Performance Improvements
> ---------------------------------------
>
>                 Key: JS2-1324
>                 URL: https://issues.apache.org/jira/browse/JS2-1324
>             Project: Jetspeed 2
>          Issue Type: Improvement
>          Components: Security
>    Affects Versions: 2.3.0
>            Reporter: David Sean Taylor
>            Assignee: Randy Watler
>             Fix For: 2.3.0
>
>
> The Security Model caches security principals and associations in the user session once initiated. Basically leveraging the session as a PRIVATE cache. However a large number of the database requests we reviewed involve fetching roles which are shared by users. The Security model however does not have a PUBLIC cache to store this type of shared information (role principals and associations) and therefore every user will query this same data.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)