Mailing-List: contact commits-help@cassandra.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cassandra.apache.org
Date: Tue, 24 Oct 2017 09:56:03 +0000 (UTC)
From: "Sam Tunnicliffe (JIRA)" <jira@apache.org>
To: commits@cassandra.apache.org
Message-ID: <JIRA.13047823.1488492284000.43612.1508838963324@Atlassian.JIRA>
In-Reply-To: <JIRA.13047823.1488492284000@Atlassian.JIRA>
References: <JIRA.13047823.1488492284000@Atlassian.JIRA> <JIRA.13047823.1488492284830@jira-lw-us.apache.org>
Subject: [jira] [Commented] (CASSANDRA-13291) Replace usages of
 MessageDigest with Guava's Hasher
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Tue, 24 Oct 2017 09:56:11 -0000


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

Sam Tunnicliffe commented on CASSANDRA-13291:
---------------------------------------------

[~mkjellman] thanks for that, I think it was definitely worth clarifying that this is really all about the server to server stuff and that anything concerning client comms is out of scope. Thanks for fixing {{computeResultMetadataId}}, I don't feel super-strongly about {{GuidGenerator}} so with that I'm +1 on the changes.
Thanks again!


> Replace usages of MessageDigest with Guava's Hasher
> ---------------------------------------------------
>
>                 Key: CASSANDRA-13291
>                 URL: https://issues.apache.org/jira/browse/CASSANDRA-13291
>             Project: Cassandra
>          Issue Type: Improvement
>          Components: Core
>            Reporter: Michael Kjellman
>            Assignee: Michael Kjellman
>         Attachments: CASSANDRA-13291-trunk.diff
>
>
> During my profiling of C* I frequently see lots of aggregate time across threads being spent inside the MD5 MessageDigest implementation. Given that there are tons of modern alternative hashing functions better than MD5 available -- both in terms of providing better collision resistance and actual computational speed -- I wanted to switch out our usage of MD5 for alternatives (like adler128 or murmur3_128) and test for performance improvements.
> Unfortunately, I found given the fact we use MessageDigest everywhere --  switching out the hashing function to something like adler128 or murmur3_128 (for example) -- which don't ship with the JDK --  wasn't straight forward.
> The goal of this ticket is to propose switching out usages of MessageDigest directly in favor of Hasher from Guava. This means going forward we can change a single line of code to switch the hashing algorithm being used (assuming there is an implementation in Guava).


--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cassandra.apache.org
For additional commands, e-mail: commits-help@cassandra.apache.org