Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Sun, 26 Apr 2015 19:30:24 +0200
From: magnum <john.magnum@...hmail.com>
To: john-dev@...ts.openwall.com
Subject: Re: [GSoC] JtR SIMD support enhancements

On Thu, Apr 23, 2015 at 11:35:44PM +0800, Lei Zhang wrote:
> Benchmarking: nt2, NT [MD4 512/512 MIC 16x]... DONE
> Raw:	4907K c/s real, 4907K c/s virtual

So this is one 1 GHz core running AVX-512. Here's my 2.3 GHz laptop 
running AVX:

Benchmarking: nt2, NT [MD4 128/128 AVX 4x3]... DONE
Raw:	43748K c/s real, 43748K c/s virtual

Accounting only for clock and width, the MIC should do 83519K. What is 
it that makes it 17x slower than that figure?


Comparing a slow hash and threads, here's MIC's md5crypt:

Benchmarking: md5crypt, crypt(3) $1$ [MD5 512/512 MIC 16x]... (240xOMP) DONE
Raw:	864932 c/s real, 3627 c/s virtual

And here's mine (4 cores + HT):

$ ../run/john -test -form:md5crypt
Will run 8 OpenMP threads
Benchmarking: md5crypt, crypt(3) $1$ [MD5 128/128 AVX 4x3]... (8xOMP) DONE
Raw:	159360 c/s real, 22102 c/s virtual

MIC should do 9127K if only clock and width was different. The real 
figure is 10x slower than that. Why?

magnum


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.