You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Jeremy Hanna (JIRA)" <ji...@apache.org> on 2019/06/13 18:29:10 UTC
[jira] [Updated] (CASSANDRA-11516) Make max number of streams
configurable
[ https://issues.apache.org/jira/browse/CASSANDRA-11516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeremy Hanna updated CASSANDRA-11516:
-------------------------------------
Complexity: Low Hanging Fruit
> Make max number of streams configurable
> ---------------------------------------
>
> Key: CASSANDRA-11516
> URL: https://issues.apache.org/jira/browse/CASSANDRA-11516
> Project: Cassandra
> Issue Type: New Feature
> Components: Legacy/Streaming and Messaging, Local/Config
> Reporter: Sebastian Estevez
> Assignee: Giampaolo
> Priority: Normal
> Labels: lhf
>
> Today we default to num cores. In large boxes (many cores), this is suboptimal as it can generate huge amounts of garbage that GC can't keep up with.
> Usually we tackle issues like this with the streaming throughput levers but in this case the problem is CPU consumption by StreamReceiverTasks specifically in the IntervalTree build -- https://github.com/apache/cassandra/blob/cassandra-2.1.12/src/java/org/apache/cassandra/utils/IntervalTree.java#L257
> We need a max number of parallel streams lever to hanlde this.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org