[infinispan-issues] [JBoss JIRA] (ISPN-3661) Allow getting entry for key and suggesting it is placed into L1 cache

[Mircea Markus (JIRA)]

     [ https://issues.jboss.org/browse/ISPN-3661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Mircea Markus updated ISPN-3661:
--------------------------------

    Component/s: L1

    
> Allow getting entry for key and suggesting it is placed into L1 cache
> ---------------------------------------------------------------------
>
>                 Key: ISPN-3661
>                 URL: https://issues.jboss.org/browse/ISPN-3661
>             Project: Infinispan
>          Issue Type: Enhancement
>          Components: L1
>            Reporter: Randall Hauch
>            Assignee: Mircea Markus
>
> When running a distributed cache, some entries are far more popular and keeping them in L1 cache on all/most nodes would enable far better locality. This can be done with a custom hashing algorithm, except when the keys do not have enough information for the algorithm to know which entries should be placed into L1. Therefore, Infinispan should offer a way for clients to get an entry by key and simultaneously request that the resulting entry be placed into the local L1 cache. For example, perhaps {{get(K key, boolean cache)}} or even {{Cache.getL1cache().get(K key)}}. 
> Here's a concrete example. ModeShape stores a tree structure in Infinispan, with keys that are basically UUIDs + other information. A common access pattern is to navigate from the root node, so it would be very useful to have the top nodes locally cached in L1 on each of the processes in the cluster (as they are accessed). ModeShape knows during access where in the tree the node is, and thus can decide the node is high enough in the tree that the node's entry be cached into L1. 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira