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

Ariel Weisberg updated CASSANDRA-19596:
---------------------------------------
    Attachment: jira-message-CASSANDRA-19596.txt

> Improve IntervalTree build throughput
> -------------------------------------
>
>                 Key: CASSANDRA-19596
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-19596
>             Project: Apache Cassandra
>          Issue Type: Improvement
>          Components: Local/Compaction, Local/SSTable
>            Reporter: Ariel Weisberg
>            Assignee: Ariel Weisberg
>            Priority: Normal
>             Fix For: 4.0.x, 4.1.x, 5.0.x, 5.x
>
>         Attachments: IntervalTreePerfTest.java, 
> ci_summary-cassandra-5.0-dd23271944aa72b294054cab270c3e8f22100668.html, 
> ci_summary-trunk-b7ce75905807bde673382799f3c3bf247802bba4.html, 
> ci_summary.html, trunk_ci_summary.html
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> 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: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to