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

Jonathan Ellis edited comment on CASSANDRA-4894 at 12/19/12 9:16 PM:
---------------------------------------------------------------------

How about this?

Compacted 4 sstables to 
[/Users/yuki/.ccm/1.2/node1/data/system/local/system-local-ia-18-Data.db,]. 957 
bytes to 629 (~65% of original) in 35ms = 0.017139MB/s. 4 total rows, 1 unique. 
Row merge counts are {1:0, 2:0, 3:0, 4:1}
                
      was (Author: jbellis):
    How about this?

Compacted 4 sstables to 
[/Users/yuki/.ccm/1.2/node1/data/system/local/system-local-ia-18-Data.db,]. 957 
bytes to 629 (~65% of original) in 35ms = 0.017139MB/s. 4 total rows, 1 unique. 
Merge counts {1:0, 2:0, 3:0, 4:1}
                  
> log number of combined/merged rows during a compaction
> ------------------------------------------------------
>
>                 Key: CASSANDRA-4894
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-4894
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Matthew F. Dennis
>            Assignee: Yuki Morishita
>            Priority: Minor
>             Fix For: 1.2.1
>
>         Attachments: 4894-1.2.txt
>
>
> we already log some details about compactions but it would be useful to know 
> how many rows were merged (resulting in "useful" work) and how many were 
> unique (representing "wasted work").
> the simple approach requires two additional counters (one for unique rows, 
> one for merged rows).  As the merge join is progressing if two or more rows 
> are combined, tick the joined counter.  If a row is simply copied tick the 
> unique counter.
> a more complete solution would be to keep a separate count for each number of 
> merges.  This would require number_of_files_being_merged counters.  If no 
> rows were merged, tick counters[0], if two rows were merged tick counters[1] 
> and so on 

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to