Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20150531032047.GA10789@openwall.com>
Date: Sun, 31 May 2015 06:20:47 +0300
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: Re: bitslice SHA-256

Hi Alain,

On Sat, May 30, 2015 at 11:06:05PM -0400, Alain Espinosa wrote:
> Just done. Attached new version of code. Included is hand-crafted Microsoft MASM assembler code for bitslice AVX2 sha256. Benchmark configuration is Windows 8.1, Visual Studio 2013, Core i5-4670 3.4GHz, only one thread. Performance is given in millions of keys per second:
> 
> - 23.7 : Normal   SHA256 implemented with hand-crafted AVX2 assembly
> - 19.5 : Bitslice SHA256 implemented with hand-crafted AVX2 assembly (22% slower than normal, 56% faster than intrinsics)
> - 12.5 : Bitslice SHA256 implemented with AVX2 intrinsics  
> 
> To give an idea of how this may traduce into real-world cracking speed, Hash Suite 3.3 cracks Raw-SHA256 at 24.8M.

I don't understand: why is Hash Suite 3.3's speed slightly higher than
the 23.7M you mentioned above?  If it's for 4 cores vs. 1 core, then why
is so much overhead incurred (almost 4x)?

Thanks,

Alexander

Powered by blists - more mailing lists

Confused about mailing lists and their use? Read about mailing lists on Wikipedia and check out these guidelines on proper formatting of your messages.