cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <>
Subject [jira] [Commented] (CASSANDRA-13063) Too many instances of BigVersion
Date Wed, 21 Dec 2016 14:31:58 GMT


Sylvain Lebresne commented on CASSANDRA-13063:

bq. I'd be wary of enumising it for fear of making further extension less flexible and more

I certainly don't care if we change this or not, but I don't see how that would make anything
less extensible since we currently already pretty much hardcode version strings. I'm not in
any way suggesting enumising {{Version}}, just {{BigVersion}}, and that would be totally internal
to the class. 

> Too many instances of BigVersion
> --------------------------------
>                 Key: CASSANDRA-13063
>                 URL:
>             Project: Cassandra
>          Issue Type: Improvement
>            Reporter: Simon Zhou
>            Assignee: Simon Zhou
>            Priority: Minor
> When debugging with Cassandra 3.0.10 I found 70+ BigVersion objects on a new node after
. This was from a cluster created by CMM and had very little data. Since we create a new instance
of BigVersion for each SSTable, that would create too many objects, eg, when bootstrapping
new node in a cluster with many sstables.
> Looks like sstables can actually share the same BigVersion instance as long as they has
same version. What we can do is to create a object cache and only create new object if not
> {code}
> ConcurrentHashMap<String, BigVersion> versions = new ConcurrentHashMap<>();
> {code}
> May not be a big deal but a minor improvement.  [~tjake] what do you think?

This message was sent by Atlassian JIRA

View raw message