Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Wed, 12 Aug 2015 23:45:35 +0200
From: magnum <>
Subject: Re: PHC: Argon2 on GPU

On 2015-08-12 18:32, Agnieszka Bielec wrote:
> I wanted to do tests on super but I discovered that final speed and
> reported when computng gws differs, don't know which is good
> [ run]$ ./john --test --format=argon2d-opencl --v=4
> Benchmarking: argon2d-opencl [Blake2 OpenCL]...
> memory per hash : 1.46 MB
> Device 0: Tahiti [AMD Radeon HD 7900 Series]
> Calculating best global worksize (GWS); max. 1s single kernel invocation.
> gws:       256         964 c/s         964 rounds/s 265.514ms per crypt_all()!
> gws:       512        1878 c/s        1878 rounds/s 272.497ms per crypt_all()+
> gws:      1024        3447 c/s        3447 rounds/s 297.022ms per crypt_all()+
> Local worksize (LWS) 64, global worksize (GWS) 1024
> using different password for benchmarking
> Speed for cost 1 (t) of 1, cost 2 (m) of 1500, cost 3 (l) of 1
> Many salts:     2925 c/s real, 307200 c/s virtual
> Only one salt:  2898 c/s real, 307200 c/s virtual

The benchmark figures (last two lines) are the correct ones. If you set 
up auto-tune correctly, that speed should be similar to the benchmark. 
For some formats/situations this is hard to achieve and it's just 
cosmetic anyway.


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.