You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cassandra.apache.org by "Dave Brosius (Issue Comment Edited) (JIRA)" <ji...@apache.org> on 2012/03/24 06:31:30 UTC

[jira] [Issue Comment Edited] (CASSANDRA-3772) Evaluate Murmur3-based partitioner

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

Dave Brosius edited comment on CASSANDRA-3772 at 3/24/12 5:31 AM:
------------------------------------------------------------------

new patch against trunk using MurmurHash.hash3_x64_128.

Preliminary testing shows murmur3 hash to be marginally faster than md5, altho not significantly. (this is on very pedestrian hardware tho, so that might mask differences). Running longer tests now to see if jit has had a fair chance to do it's magic.
                
      was (Author: dbrosius@apache.org):
    new patch against trunk using MurmurHash.hash3_x64_128.

Preliminary testing show murmur3 hash to be marginally faster than md5, altho not significantly. (this is one very pedestrian hardware tho, so that might mask differences). Running longer tests now to see if jit has had a fair chance to do it's magic.
                  
> 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: 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