[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <BLU0-SMTP16065EAA11FC9B4005970AFFDE30@phx.gbl>
Date: Sat, 23 Jun 2012 22:05:46 +0200
From: Frank Dittrich <frank_dittrich@...mail.com>
To: john-dev@...ts.openwall.com
Subject: Re: relbench and changed format names
On 06/22/2012 12:49 AM, Solar Designer wrote:
>> Benchmarking: MySQL [32/32 (label mysql-fast)]... DONE
>
> Will be:
>
> MySQL (label mysql-fast)
Another option, let it be just MySQL, move
MySQL (label mysql) to unused, let benchmark-unify map all possible
names of older versions (MYSQL and MYSQL_fast) to MySQL, and let
relbench pick the fastest benchmark it finds for that format for the
comparison.
>> Benchmarking: NT MD4 [128/128 SSE2 + 32/32]... DONE
>
> NT MD4 (label nt)
>
>> Benchmarking: NT MD4 [128/128 SSE2 intrinsics 12x]... DONE
>
> NT MD4 (label nt2)
Here, I agree
>> Benchmarking: Raw SHA-1 [128/128 SSE2 intrinsics 8x]... DONE
>
> Raw SHA-1 (label raw-sha1)
>
>> Benchmarking: Raw SHA-1 [128/128 SSE2 intrinsics 4x]... DONE
>
> Raw SHA-1 (label raw-sha1-ng)
Since raw-sha1-ng supports a smaller maximum password length, I would
make that more obvious and vote for
Raw SHA-1
vs.
Raw SHA-1 (maxlen 15)
or something similar.
Frank
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.
