[infinispan-issues] [JBoss JIRA] (ISPN-4979) CacheStatusResponse map uses too much memory

[William Burns (JIRA)]

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

William Burns commented on ISPN-4979:
-------------------------------------

I have added in reuse of CacheTopologies that are equal in the returned CacheStatusResponse and in my test this reduce the overall size by a substantial amount with both changes (my small test reduced size anywhere from 20-35 times smaller).  This optimization will work best when you have a number of caches that share the same number of segments and owner nodes and/or if you have a large amount of nodes.

There is still an issue where a couple tests have an issue with topology changes that needs to be investigated.

> CacheStatusResponse map uses too much memory
> --------------------------------------------
>
>                 Key: ISPN-4979
>                 URL: https://issues.jboss.org/browse/ISPN-4979
>             Project: Infinispan
>          Issue Type: Bug
>          Components: Core, State Transfer
>    Affects Versions: 7.0.0.Final
>            Reporter: Dan Berindei
>            Assignee: William Burns
>            Priority: Critical
>             Fix For: 7.1.0.Final
>
>
> When the cluster is large and there are a log of caches, the {{CacheStatusResponse}} map on the new coordinator can get quite large. One of the problems that seems to be that the addresses in {{DefaultConsistentHash}} are duplicated on serialization, so the deserialized version occupies more memory.
> We need to investigate why the objects are not "shared" by the River marshaller, and maybe work around the problem by de-duplicating the addresses in the externalizer.



--
This message was sent by Atlassian JIRA
(v6.3.8#6338)