Uploaded image for project: 'Infinispan'
  1. Infinispan
  2. ISPN-3229

L1 cache entries should not be passivated


    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • 7.0.0.Beta2
    • 5.2.6.Final
    • L1
    • None

      L1 entries are stored in the same data container as the real entries. These can be evicted which is fine, however we don't want them to be passivated as this could be costly to write/read from the cache store. We should either prevent L1 cache entries from being passivated or have an option to allow for it.

      Currently L1 entries are not differentiated from other entries except through the fact that they are mortal, which is used for other operations as well, which means they would need a placeholder of some kind to tell the container this is a L1 entry.

            wburns@redhat.com Will Burns
            wburns@redhat.com Will Burns
            0 Vote for this issue
            2 Start watching this issue