[jira] [Commented] (CASSANDRA-3772) Evaluate Murmur3-based partitioner

["Jonathan Ellis (JIRA)" <ji...@apache.org>]

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

Jonathan Ellis commented on CASSANDRA-3772:
-------------------------------------------

bq. Did you guys tested on secondary index reads (with reasonably high cardinality)? That's when MD5 was a bottleneck because then the column comparator ends up redecorating keys over and over again.

Is that something we can address in the index code then, instead of creating a new partitioner?


                
> Evaluate Murmur3-based partitioner
> ----------------------------------
>
>                 Key: CASSANDRA-3772
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-3772
>             Project: Cassandra
>          Issue Type: New Feature
>          Components: Core
>            Reporter: Jonathan Ellis
>            Assignee: Dave Brosius
>             Fix For: 1.2
>
>         Attachments: 0001-CASSANDRA-3772-Test.patch, MumPartitionerTest.docx, hashed_partitioner.diff, hashed_partitioner_3.diff, try_murmur3.diff, try_murmur3_2.diff
>
>
> MD5 is a relatively heavyweight hash to use when we don't need cryptographic qualities, just a good output distribution.  Let's see how much overhead we can save by using Murmur3 instead.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira