[
https://issues.apache.org/jira/browse/SHIRO-317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17276099#comment-17276099
]
Chitral Verma commented on SHIRO-317:
-------------------------------------
{quote}There are still about 11 calls to the cache in one request.
{quote}
[~bytor99999] I know this is a really old, but the magical 11 hits are still
there. I was writing a shiro-redis implementation (for end users) and got stuck
in this.I also saw that every change on the session object is persisted
immediately to the cache and thats why there propotionate number of update
calls as well.
My solution is also to use a thread local delegating version of cache, but in
case of load, there are chances of OOM considering end users may store huge
objects as session attributes.
[~lhazlewood]
Is there any resolution for this? Or maybe can the softmap pattern be a
standard interface? I can help with the implementation if required.
> Read session from cache once per request
> ----------------------------------------
>
> Key: SHIRO-317
> URL: https://issues.apache.org/jira/browse/SHIRO-317
> Project: Shiro
> Issue Type: New Feature
> Affects Versions: 1.1.0, 1.2.0, 1.2.1
> Reporter: Luke Biddell
> Assignee: Les Hazlewood
> Priority: Minor
>
> As per our discussion on the mailing thread, I've wired up my sessions to be
> stored in memcached (membase in the longer term). On a per request basis I'm
> seeing approximately 5 hits on my cache to retrieve the session. I would
> expect to see only one hit per threaded request, with the session stored as a
> thread local.
> For distributed caches this saves on network calls and for local caches it
> will save on potential lock contention.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
