[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAJpaVcQGQhQT8mVg6y+i6MoSpD4_vXTokvTDaPX-0u2=21ceAA@mail.gmail.com>
Date: Sat, 26 Jan 2013 04:12:50 -0500
From: Brian Wallace <nightstrike9809@...il.com>
To: john-dev@...ts.openwall.com
Subject: Re: Proposed optimizations to pwsafe
Something I noticed when benchmarking. For some reason, CUDA runs slower
in bleeding than unstable.
On Sat, Jan 26, 2013 at 2:29 AM, Brian Wallace <nightstrike9809@...il.com>wrote:
> I have some working improvements to pwsafe-cuda. I don't have the most
> powerful GPU, but the improvement so far is as follows:
>
> Original:
> Benchmarking: Password Safe SHA-256 [CUDA]... DONE
> Raw: 51801 c/s real, 51801 c/s virtual
>
> New:
> Benchmarking: Password Safe SHA-256 [CUDA]... DONE
> Raw: 70593 c/s real, 70593 c/s virtual
>
> I do see some other improvements I can make though.
>
> On Fri, Jan 25, 2013 at 8:05 PM, Solar Designer <solar@...nwall.com>wrote:
>
>> On Fri, Jan 25, 2013 at 05:55:38AM +0100, Lukas Odzioba wrote:
>> > 2013/1/21 Solar Designer <solar@...nwall.com>:
>> > > hashcat's is better, too (354k vs. 501k). Lukas?
>> >
>> > I have an idea what's need to be done to improve this and some others
>> > sha256 formats.
>> > The problem is that I will not have time for that in the next 3 weeks
>> > because of exams.
>> > I planned for this weekend some other minor/trivial changes that I
>> > think we need before jumbo release, but that's all what I can do at
>> > the moment.
>> > I added this task next to gpu pbkdf2-sha512 to my todo list.
>>
>> Sounds fine. Meanwhile:
>>
>> <gat3way> OK I am in the pwsafe game too. @hashcat you beat me by several
>> K c/s :) http://t.co/CIXK83FT
>>
>> http://twitter.com/gat3way/status/294968226209726464/photo/1
>>
>> Alexander
>>
>
>
Content of type "text/html" skipped
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.
