[
https://issues.apache.org/jira/browse/CASSANDRA-19808?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cesar Andres Stuardo Moraga updated CASSANDRA-19808:
----------------------------------------------------
Summary: Gossiper (micro) optmizations (was: Gossiper optmizations)
> Gossiper (micro) optmizations
> -----------------------------
>
> Key: CASSANDRA-19808
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19808
> Project: Cassandra
> Issue Type: Improvement
> Reporter: Cesar Andres Stuardo Moraga
> Priority: Normal
>
> I am wondering about optimizations that can be done in the gossiper class,
> especially targeting performance at larger scales.
> # getLiveMembers: Creating a hashmap every time this is called. Aside from
> creating some trash, its linear in terms of the number of peers.
> # getMaxEndpointStateVersion: I feel this can be calculated and cached
> rather than looking for it. It is also linear on the number of peers.
> # getGossipStatus: Linear in the number of peers, also source of garbage at
> larger scales.
> It seems optmizing these methods can contribute to a cleaner/performant
> membership protocol. Is there any plans on having these types of optmizations?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
