[infinispan-issues] [JBoss JIRA] (ISPN-8862) Iteration and stream operations with passivation disabled shouldn't use in memory

[William Burns (Jira)]

    [ https://issues.jboss.org/browse/ISPN-8862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13668327#comment-13668327 ] 

William Burns commented on ISPN-8862:
-------------------------------------

You are saying keep track if an entry was evicted in the data container when passivation is enabled and if not then only do iteration over the data container, correct?

Yeah iterating over the store keys vs keys and value is interesting, but we have no way to do that currently and putting that logic into the store will complicate them all substantially. To be honest I don't know if there is a good answer

> Iteration and stream operations with passivation disabled shouldn't use in memory
> ---------------------------------------------------------------------------------
>
>                 Key: ISPN-8862
>                 URL: https://issues.jboss.org/browse/ISPN-8862
>             Project: Infinispan
>          Issue Type: Enhancement
>            Reporter: William Burns
>            Assignee: William Burns
>            Priority: Major
>             Fix For: 9.4.4.Final
>
>
> When passivation is disabled all entries are assumed to be in the cache loader/store. We currently try to merge these together in a sloppy way [1]. This first reads in memory and then from the store and keeps all keys from in memory to exclude them from the store. Unfortunately the store still has to pull the entries even for the already read keys, but just ignores them. This leads to a lot of inefficiency and memory bloat. Instead we should just return the store entries as is when passivation is disabled.
> [1] https://github.com/infinispan/infinispan/blob/master/core/src/main/java/org/infinispan/interceptors/impl/CacheLoaderInterceptor.java#L506



--
This message was sent by Atlassian Jira
(v7.12.1#712002)