You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@cassandra.apache.org by "Ariel Weisberg (Jira)" <ji...@apache.org> on 2024/05/09 19:24:00 UTC

[jira] [Updated] (CASSANDRA-19596) IntervalTree build throughput is low enough to be a bottleneck

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

Ariel Weisberg updated CASSANDRA-19596:
---------------------------------------
    Change Category: Performance
         Complexity: Low Hanging Fruit
      Fix Version/s: 5.x
             Status: Open  (was: Triage Needed)

> IntervalTree build throughput is low enough to be a bottleneck
> --------------------------------------------------------------
>
>                 Key: CASSANDRA-19596
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19596
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Local/Compaction, Local/SSTable
>            Reporter: Ariel Weisberg
>            Assignee: Ariel Weisberg
>            Priority: Normal
>             Fix For: 5.x
>
>
> With several terabytes of data and 8 compactors it’s possible for the compactors to spend a lot of time blocked waiting on IntervalTrees to be built.
> There is also a lot of wasted CPU because it’s updated optimistically so most of them end up being thrown away.
> This can end up being quite painful because it can block memtable flushing as well and then a single slow CFS can block unrelated CFS because the memtable post flush executor is single threaded and shared across all CFS. 



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org