cassandra-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sylvain Lebresne (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CASSANDRA-8918) Optimise compaction performance for unique partition keys
Date Thu, 05 Mar 2015 16:07:40 GMT

    [ https://issues.apache.org/jira/browse/CASSANDRA-8918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14348996#comment-14348996
] 

Sylvain Lebresne commented on CASSANDRA-8918:
---------------------------------------------

Do you mean keeping all of our stats on a per-partition basis? If so, I would suspect it would
get pretty big pretty fast.

> Optimise compaction performance for unique partition keys
> ---------------------------------------------------------
>
>                 Key: CASSANDRA-8918
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-8918
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Benedict
>             Fix For: 3.0
>
>
> Related to the raft of improvements we're looking at for improving the CPU burden of
merge, if we can demonstrate that an entire partition key is unique to a given file (which
is quite easily done) we can avoid materialising any of the row, and simply copy the data
wholesale, with potentially some small modifications to the index file data if it has clustering
column index entries, and special treatment of tombstones (most simple would be to only check
there are no tombstones to purge, and abort this approach if so).



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message