Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20120120201224.GA8188@openwall.com>
Date: Sat, 21 Jan 2012 00:12:24 +0400
From: Solar Designer <solar@...nwall.com>
To: john-users@...ts.openwall.com
Subject: Re: DES with OpenMP

On Sat, Dec 31, 2011 at 08:32:43PM +0000, Alex Sicamiotis wrote:
> For the time being, I'm absolutely "settled" with the icc openmp version.

You may also try gcc 4.3.6 with DES_BS_ASM set to 0 (or OpenMP enabled).
It turns out that gcc's performance regressions at this code started
between 4.3.x and 4.4.0:

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=51017

4.1.0 - 2959K c/s, 28182 bytes
4.1.2 - 2964K c/s, 28365 bytes
4.2.0 - 2968K c/s, 28363 bytes
4.2.4 - 2971K c/s, 28382 bytes
4.3.0 - 2971K c/s, 28229 bytes
4.3.6 - 2959K c/s, 28229 bytes
4.4.0 - 2625K c/s, 29770 bytes
4.4.6 - 2695K c/s, 29316 bytes
4.5.0 - 2729K c/s, 29203 bytes
4.5.3 - 2716K c/s, 29203 bytes
4.6.0 - 2111K c/s, 29624 bytes
4.6.2 - 2123K c/s, 29624 bytes

So thing were really good for versions 4.1.0 through 4.3.6, but started
to get worse afterwards and got really bad with 4.6.

To be fair, things are very different for some other hash/cipher types
supported by JtR - e.g., for Blowfish-based hashing we went from 560 c/s
for 4.1.0 to 700 c/s for 4.6.2.

The above figures are for a 2.5 GHz Core 2'ish core.  With DES_BS_ASM 1
(the default in 1.7.9 for non-OpenMP builds), the same CPU gives 2780K c/s
(faster than gcc 4.4+, but slower than gcc 4.1 through 4.3.x).

I think with gcc 4.3.6 you might get up to 4750K c/s on one core in your
Celeron E3200 at 4.0 GHz, and you might cross 9000K c/s with OpenMP.

Alexander

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.