You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jonathan Ellis (JIRA)" <ji...@apache.org> on 2013/12/03 04:31:35 UTC

[jira] [Updated] (CASSANDRA-6410) gossip memory usage improvement

     [ https://issues.apache.org/jira/browse/CASSANDRA-6410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Jonathan Ellis updated CASSANDRA-6410:
--------------------------------------

    Fix Version/s:     (was: 1.2.13)

... I'm going to back this out of 1.2 since Java6 has serious issues with heavy usage of {{intern}}.  I'll also add a {{-XX:StringTableSize}} option to 2.0.  More details at http://java-performance.info/string-intern-in-java-6-7-8/.

> gossip memory usage improvement
> -------------------------------
>
>                 Key: CASSANDRA-6410
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-6410
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Quentin Conner
>            Assignee: Jonathan Ellis
>            Priority: Minor
>             Fix For: 2.0.4
>
>         Attachments: 6410-EnumMap.txt, gossip-intern.txt
>
>
> It looks to me that any given node will need ~2 MB of Java VM heap for each other node in the ring.  This was observed with num_tokens=512 but still seems excessive.



--
This message was sent by Atlassian JIRA
(v6.1#6144)