[
https://issues.jboss.org/browse/ISPN-8862?page=com.atlassian.jira.plugin....
]
William Burns commented on ISPN-8862:
-------------------------------------
The other issue with the former idea is if we had a passivation during the iteration
process we could miss an entry :( Thus we would have to listen to passivations and if did
happen compare if we already returned that key, which is exactly what we do currently :(
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/o...
--
This message was sent by Atlassian Jira
(v7.12.1#712002)