[infinispan-issues] [JBoss JIRA] (ISPN-8862) Iteration and stream operations with passivation disabled shouldn't use in memory
William Burns (JIRA)
issues at jboss.org
Mon Feb 26 10:17:00 EST 2018
[ https://issues.jboss.org/browse/ISPN-8862?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13538303#comment-13538303 ]
William Burns commented on ISPN-8862:
-------------------------------------
Looking at this more, I think this is a bit more complicated. If we have all entries in memory that we have in the store, this change would cause a very big performance degredation in my testing with a SingleFileStore (45 op/s down to .67 op/s).
This should be optionally done based on if off heap/store as binary/eviction/preload and other factors. This needs to be thought out more.
> 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
> Fix For: 9.3.0.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.5.0#75005)
More information about the infinispan-issues
mailing list