Follow @Openwall on Twitter for new release announcements and other news
[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Date: Wed, 11 Apr 2012 08:06:44 +0400
From: Solar Designer <solar@...nwall.com>
To: john-dev@...ts.openwall.com
Subject: OpenCL tests on GTX 570

magnum, Lukas, Sayantan, Samuele -

Here's a full set of OpenCL tests for magnum-jumbo on my GTX 570 1600 MHz.
(I ran these one by one because we do not yet have "format destructors"
and because a segfault or the like would prevent further tests.)

user@...l:~/john/magnum-jumbo/src$ ../run/john -te -fo=cryptmd5-opencl
OpenCL platform 0: NVIDIA CUDA, 1 device(s).
Using device 0: GeForce GTX 570
OpenCL error (CL_INVALID_VALUE) in file (common-opencl.c) at line (128) - (Error while getting build info)

---

user@...l:~/john/magnum-jumbo/src$ ../run/john -te -fo=cryptsha512-opencl
OpenCL platform 0: NVIDIA CUDA, 1 device(s).
Using device 0: GeForce GTX 570
Segmentation fault (core dumped)

---

user@...l:~/john/magnum-jumbo/src$ ../run/john -te -fo=mscash2-opencl
OpenCL platform 0: NVIDIA CUDA, 1 device(s).
Using device 0: GeForce GTX 570
Benchmarking: MSCASH2-OPENCL [PBKDF2_HMAC_SHA1]... DONE
Raw:    14050 c/s real, 14035 c/s virtual

(This is roughly twice slower than Lukas' CUDA code.)

---

user@...l:~/john/magnum-jumbo/src$ ../run/john -te -fo=mysql-sha1-opencl
OpenCL platform 0: NVIDIA CUDA, 1 device(s).
Using device 0: GeForce GTX 570
Max Group Work Size 1024 Error -5
Optimal local work size 64
(to avoid this test on next run do export LWS=64)
Local work size (LWS) 64, Keys per crypt (KPC) 2097152
Benchmarking: MySQL 4.1 double-SHA-1 [mysql-sha1-opencl]... DONE
Many salts:     24197K c/s real, 24013K c/s virtual
Only one salt:  23301K c/s real, 23301K c/s virtual

---

user@...l:~/john/magnum-jumbo/src$ ../run/john -te -fo=nt-opencl
OpenCL platform 0: NVIDIA CUDA, 1 device(s).
Using device 0: GeForce GTX 570
Optimal Local work size 128
Benchmarking: NT MD4 [OpenCL 1.0]... DONE
Raw:    37832K c/s real, 37618K c/s virtual

---

user@...l:~/john/magnum-jumbo/src$ ../run/john -te -fo=phpass-opencl
OpenCL platform 0: NVIDIA CUDA, 1 device(s).
Using device 0: GeForce GTX 570
OpenCL error (CL_OUT_OF_RESOURCES) in file (opencl_phpass_fmt.c) at line (162) - (Run kernel)

---

user@...l:~/john/magnum-jumbo/src$ ../run/john -te -fo=raw-md5-opencl
OpenCL platform 0: NVIDIA CUDA, 1 device(s).
Using device 0: GeForce GTX 570
Max Group Work Size 1024 Optimal local work size 128
(to avoid this test on next run do export LWS=128)
Local work size (LWS) 128, Keys per crypt (KPC) 2097152
Benchmarking: Raw MD5 [raw-md5-opencl]... DONE
Raw:    48880K c/s real, 48880K c/s virtual

---

user@...l:~/john/magnum-jumbo/src$ ../run/john -te -fo=raw-sha1-opencl
OpenCL platform 0: NVIDIA CUDA, 1 device(s).
Using device 0: GeForce GTX 570
Max Group Work Size 1024 Optimal local work size 64
(to avoid this test on next run do export LWS=64)
Local work size (LWS) 64, Keys per crypt (KPC) 2097152
Benchmarking: Raw SHA-1 OpenCL [raw-sha1-opencl]... DONE
Raw:    47109K c/s real, 47453K c/s virtual

---

user@...l:~/john/magnum-jumbo/src$ ../run/john -te -fo=ssha-opencl
OpenCL platform 0: NVIDIA CUDA, 1 device(s).
Using device 0: GeForce GTX 570
Max Group Work Size 1024 Optimal local work size 64
(to avoid this test on next run, put "ssha_LWS = 64" in john.conf, section [Options:OpenCL])
Local work size (LWS) 64, Keys per crypt (KPC) 4194304
Benchmarking: Netscape LDAP SSHA OPENCL [salted SHA-1]... DONE
Many salts:     66001K c/s real, 66001K c/s virtual
Only one salt:  46603K c/s real, 46603K c/s virtual

---

user@...l:~/john/magnum-jumbo/src$ ../run/john -te -fo=rar
OpenCL platform 0: NVIDIA CUDA, 1 device(s).
Using device 0: GeForce GTX 570
Max allowed local work size 576, best multiple 32
Local work size (LWS) 512, Keys per crypt (KPC) 8192
Benchmarking: RAR3 (6 characters) [OpenCL]... (8xOMP) DONE
Raw:    2259 c/s real, 2211 c/s virtual

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.