[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CALW8-7J-cZiphedsHz7PCRT-hfJU6PbRF0+weK5tiAG-nL6EyQ@mail.gmail.com>
Date: Wed, 19 Aug 2015 19:27:30 +0200
From: Dmitry Khovratovich <khovratovich@...il.com>
To: "discussions@...sword-hashing.net" <discussions@...sword-hashing.net>
Subject: Re: [PHC] Argon2 CPU/GPU benchmarks
>
>
>
> What do you mean by GPU portability here? Simplifying OpenCL
> implementations for testing, or for actual defensive use of GPUs?
>
Simplifying implementations for testing, in order to realize all the
possible advantages of GPU cracking earlier than the attacker does so.
>
> We don't yet exploit this (except possibly to a very limited extent that
> an OpenCL compiler and the hardware might), so I wouldn't attribute the
> current results to it. I've been thinking of communicating suggestions
> on how to try exploiting this to Agnieszka today. So we'll likely try.
> If successful, this should let us pack more concurrent instances of
> Argon2, and should provide much speedup over the results so far (as
> we're not yet bumping into memory bandwidth, by far).
>
What is the parallelism parameter BTW? p=1 for all schemes?
>
> Combined, these result in Titan X being 3072/640*1000/1096 = 4.38 times
> faster. In case memory bandwidth ever becomes the limiting factor (as
> we optimize the code more), it's similar too: 336/80 = 4.2 times faster.
>
I understand, but why do you get 37x advantage of yescrypt from there?
Don't these properties speed up yescrypt as well?
>
> > > Potential results for GTX Titan X:
> > >
> > > 2480/(1861*3072/640*1000/1096) / (4736/419) = 0.027
> > > 7808/(4227*3072/640*1000/1096) / (4736/419) = 0.037
> > >
> > > or:
> > >
> > > 4736/419 / (2480/(1861*3072/640*1000/1096)) = 37.1
> > > 4736/419 / (7808/(4227*3072/640*1000/1096)) = 26.8
>
> Alexander
>
--
Best regards,
Dmitry Khovratovich
Content of type "text/html" skipped
Powered by blists - more mailing lists