Posts: 18
Threads: 6
Joined: Jan 2011
I found plus is much slower than oclhashcat 0.26.
For cracking 700m md5 hashes.
oclhashcat 1.txt ?1?1?1?1?1 ?1?1?1?1 -1 ?l?d -o 1.out -->3300M/s
oclhashcat-plus 1.txt ?1?1?1?1?1?1?1?1?1 -1 ?l?d -o 1.out -a 3 --<2200M/s
2x hd6970.
For cracking old mysql hashes, I have to use oclhashcat 0.25 also.
Posts: 127
Threads: 16
Joined: Sep 2011
Try increasing the -n value. It makes a big difference in some cases. Also for some hash types I've found that increasing --gpu-loops helps.
Posts: 18
Threads: 6
Joined: Jan 2011
(01-02-2012, 05:15 AM)chort Wrote: Try increasing the -n value. It makes a big difference in some cases. Also for some hash types I've found that increasing --gpu-loops helps.
I tried many different parameters , but no help.
Now I changed my system date back to 2011 for oclhashcat.
Posts: 5,185
Threads: 230
Joined: Apr 2010
plus is much faster than old oclHashcat. otherwise i wouldnt have changed 700000000 hashes at once is such a huge amount of hashes that the results are unpredictable. maximum i tested was 24000000 hashes at once.
Posts: 18
Threads: 6
Joined: Jan 2011
01-02-2012, 01:55 PM
(This post was last modified: 01-02-2012, 02:18 PM by nobody.)
(01-02-2012, 11:16 AM)atom Wrote: plus is much faster than old oclHashcat. otherwise i wouldnt have changed 700000000 hashes at once is such a huge amount of hashes that the results are unpredictable. maximum i tested was 24000000 hashes at once.
Sorry I made a mistake, the number is 700000.
This is the detail information two hd5870 cards, driver 11.12, windows server 2008 r2)
Quote:T:\run\oclHashcat-plus>oclHashcat-plus64.exe 1.txt -a 3 ?1?1?1?1?1?1?1?1?1 -1 ?l?d -o 1.out
oclHashcat-plus v0.07 by atom starting...
Hashes: 701692
Unique digests: 701692
Bitmaps: 21 bits, 1048576 entries, 0x000fffff mask, 4194304 bytes
GPU-Loops: 128
GPU-Accel: 40
Password lengths range: 1 - 15
Platform: AMD compatible platform found
Watchdog: Temperature limit disabled
Device #1: Cypress, 1024MB, 0Mhz, 20MCU
Device #2: Cypress, 1024MB, 0Mhz, 20MCU
Device #1: Allocating 120MB host-memory
Device #1: Kernel ./kernels/4098/m0000_a3.Cypress.64.kernel (221300 bytes)
Device #2: Allocating 120MB host-memory
Device #2: Kernel ./kernels/4098/m0000_a3.Cypress.64.kernel (221300 bytes)
[s]tatus [p]ause [r]esume [q]uit => s
Status.......: Running
Input.Mode...: Mask (?1?1?1?1?1?1?1?1?1)
Hash.Type....: MD5
Time.Running.: 4 secs
Time.Left....: 15 hours, 0 mins
Time.Util....: 4992.5ms/43.3ms Real/CPU, 0.9% idle
Speed........: 1879.8M c/s Real, 1912.2M c/s GPU
Recovered....: 0/701692 Digests, 0/1 Salts
Progress.....: 9384755200/101559956668416 (0.01%)
Rejected.....: 0/9384755200 (0.00%)
[s]tatus [p]ause [r]esume [q]uit => q
Status.......: Aborted
Input.Mode...: Mask (?1?1?1?1?1?1?1?1?1)
Hash.Type....: MD5
Time.Running.: 9 secs
Time.Left....: 14 hours, 55 mins
Time.Util....: 9788.2ms/43.3ms Real/CPU, 0.4% idle
Speed........: 1890.8M c/s Real, 1847.3M c/s GPU
Recovered....: 0/701692 Digests, 0/1 Salts
Progress.....: 18507366400/101559956668416 (0.02%)
Rejected.....: 0/18507366400 (0.00%)
Started: Sun Jan 02 20:00:38 2011
Stopped: Sun Jan 02 20:00:49 2011
T:\run\oclHashcat-plus>cd ..
T:\run>cd oclHashcat
T:\run\oclHashcat>oclHashcat64.exe ..\oclHashcat-plus\1.txt ?1?1?1?1?1 ?1?1?1?1 -1 ?l?d
oclHashcat v0.26 by atom starting...
Digests: 701692 entries, 701692 unique
Bitmaps: 21 bits, 1048576 entries, 0x000fffff mask, 4194304 bytes
Platform: AMD compatible platform found
Watchdog: Temperature limit disabled
Device #1: Cypress, 1024MB, 0Mhz, 20MCU
Device #2: Cypress, 1024MB, 0Mhz, 20MCU
NOTE: gpu-accel auto-adjusted to: 80
Device #1: Kernel ./kernels/4098/m0000.Cypress.64.kernel
Device #2: Kernel ./kernels/4098/m0000.Cypress.64.kernel
[s]tatus [p]ause [r]esume [q]uit => s
Status.......: Running
Hash.Type....: MD5
Mode.Left....: Mask '?1?1?1?1?1' (60466176)
Mode.Right...: Mask '?1?1?1?1' (1679616)
Speed.GPU*...: 3359.9M/s
Recovered....: 0/701692 Digests, 0/1 Salts
Progress.....: 6160384000/101559956668416 (0.01%)
Running......: 1 sec
Estimated....: 8 hours, 23 mins
[s]tatus [p]ause [r]esume [q]uit => s
Status.......: Running
Hash.Type....: MD5
Mode.Left....: Mask '?1?1?1?1?1' (60466176)
Mode.Right...: Mask '?1?1?1?1' (1679616)
Speed.GPU*...: 3329.0M/s
Recovered....: 0/701692 Digests, 0/1 Salts
Progress.....: 13841203200/101559956668416 (0.01%)
Running......: 4 secs
Estimated....: 8 hours, 28 mins
[s]tatus [p]ause [r]esume [q]uit => q
Status.......: Aborted
Hash.Type....: MD5
Mode.Left....: Mask '?1?1?1?1?1' (60466176)
Mode.Right...: Mask '?1?1?1?1' (1679616)
Speed.GPU*...: 3387.3M/s
Recovered....: 0/701692 Digests, 0/1 Salts
Progress.....: 17799577600/101559956668416 (0.02%)
Running......: 5 secs
Estimated....: 8 hours, 19 mins
Started: Sun Jan 02 20:01:34 2011
Stopped: Sun Jan 02 20:01:41 2011
T:\run\oclHashcat>
Another computer(two hd6970 cards, driver 11.12 ,windows 2008 r2)
Quote:Y:\run\oclHashcat-plus>oclHashcat-plus64.exe 1.txt -a 3 ?1?1?1?1?1?1?1?1?1 -1 ?l?d -o 1.out
oclHashcat-plus v0.07 by atom starting...
Hashes: 701692
Unique digests: 701692
Bitmaps: 21 bits, 1048576 entries, 0x000fffff mask, 4194304 bytes
GPU-Loops: 128
GPU-Accel: 40
Password lengths range: 1 - 15
Platform: AMD compatible platform found
Watchdog: Temperature limit disabled
Device #1: Cayman, 2048MB, 0Mhz, 24MCU
Device #2: Cayman, 2048MB, 0Mhz, 24MCU
Device #1: Allocating 144MB host-memory
Device #1: Kernel ./kernels/4098/m0000_a3.Cayman.64.kernel (220660 bytes)
Device #2: Allocating 144MB host-memory
Device #2: Kernel ./kernels/4098/m0000_a3.Cayman.64.kernel (220660 bytes)
[s]tatus [p]ause [r]esume [q]uit => s
Status.......: Aborted
Input.Mode...: Mask (?1?1?1?1?1?1?1?1?1)
Hash.Type....: MD5
Time.Running.: 8 secs
Time.Left....: 12 hours, 38 mins
Time.Util....: 8914.7ms/61.5ms Real/CPU, 0.7% idle
Speed........: 2230.1M c/s Real, 2239.2M c/s GPU
Recovered....: 0/701692 Digests, 0/1 Salts
Progress.....: 19881000960/101559956668416 (0.02%)
Rejected.....: 0/19881000960 (0.00%)
Started: Mon Jan 02 20:14:49 2012
Stopped: Mon Jan 02 20:15:00 2012
Y:\run\oclHashcat-plus>cd ..\oclHashcat
Y:\run\oclHashcat>date 2011-01-02
Y:\run\oclHashcat>oclHashcat64.exe ..\oclHashcat-plus\1.txt ?1?1?1?1?1 ?1?1?1?1 -1 ?l?d
oclHashcat v0.26 by atom starting...
Digests: 701692 entries, 701692 unique
Bitmaps: 21 bits, 1048576 entries, 0x000fffff mask, 4194304 bytes
Platform: AMD compatible platform found
Watchdog: Temperature limit disabled
Device #1: Cayman, 2048MB, 0Mhz, 24MCU
Device #2: Cayman, 2048MB, 0Mhz, 24MCU
NOTE: gpu-accel auto-adjusted to: 80
Device #1: Kernel ./kernels/4098/m0000.Cayman.64.kernel
Device #2: Kernel ./kernels/4098/m0000.Cayman.64.kernel
[s]tatus [p]ause [r]esume [q]uit => s
Status.......: Aborted
Hash.Type....: MD5
Mode.Left....: Mask '?1?1?1?1?1' (60466176)
Mode.Right...: Mask '?1?1?1?1' (1679616)
Speed.GPU*...: 3272.6M/s
Recovered....: 0/701692 Digests, 0/1 Salts
Progress.....: 14155776000/101559956668416 (0.01%)
Running......: 4 secs
Estimated....: 8 hours, 37 mins
Started: Sun Jan 02 20:15:36 2011
Stopped: Sun Jan 02 20:15:43 2011
Y:\run\oclHashcat>date 2012-1-2
Y:\run\oclHashcat>
Posts: 5,185
Threads: 230
Joined: Apr 2010
as chort already said, increase the -n value:
oclHashcat-plus64.exe 1.txt -a 3 ?1?1?1?1?1?1?1?1?1 -1 ?l?d -o 1.out -n 80
Posts: 18
Threads: 6
Joined: Jan 2011
(01-02-2012, 03:53 PM)atom Wrote: as chort already said, increase the -n value:
oclHashcat-plus64.exe 1.txt -a 3 ?1?1?1?1?1?1?1?1?1 -1 ?l?d -o 1.out -n 80
Increasing -n or --gpu-loops does not help.
Below is two 5870.
Quote:T:\run\oclHashcat-plus>oclHashcat-plus64.exe 1.txt -a 3 ?1?1?1?1?1?1?1?1?1 -1 ?l?d -o 1.out -n 80
oclHashcat-plus v0.07 by atom starting...
Hashes: 701692
Unique digests: 701692
Bitmaps: 21 bits, 1048576 entries, 0x000fffff mask, 4194304 bytes
GPU-Loops: 128
GPU-Accel: 80
Password lengths range: 1 - 15
Platform: AMD compatible platform found
Watchdog: Temperature limit disabled
Device #1: Cypress, 1024MB, 0Mhz, 20MCU
Device #2: Cypress, 1024MB, 0Mhz, 20MCU
Device #1: Allocating 240MB host-memory
Device #1: Kernel ./kernels/4098/m0000_a3.Cypress.64.kernel (221300 bytes)
Device #2: Allocating 240MB host-memory
Device #2: Kernel ./kernels/4098/m0000_a3.Cypress.64.kernel (221300 bytes)
[s]tatus [p]ause [r]esume [q]uit => q
Status.......: Aborted
Input.Mode...: Mask (?1?1?1?1?1?1?1?1?1)
Hash.Type....: MD5
Time.Running.: 4 secs
Time.Left....: 14 hours, 32 mins
Time.Util....: 4972.4ms/85.6ms Real/CPU, 1.8% idle
Speed........: 1940.1M c/s Real, 1981.9M c/s GPU
Recovered....: 1/701692 Digests, 0/1 Salts
Progress.....: 9646899200/101559956668416 (0.01%)
Rejected.....: 0/9646899200 (0.00%)
Started: Sun Jan 02 22:49:06 2011
Stopped: Sun Jan 02 22:49:12 2011
T:\run\oclHashcat-plus>
Posts: 313
Threads: 44
Joined: Aug 2011
what is the GPU utilization at during the run?
Posts: 18
Threads: 6
Joined: Jan 2011
(01-02-2012, 08:11 PM)forumhero Wrote: what is the GPU utilization at during the run?
Gpu usage :
plus: 97% 98% or 99%.
oclhashcat 0.26: 94%
Posts: 5,185
Threads: 230
Joined: Apr 2010
since brute-force has been ported from lite and not from regular oclHashcat, speeds depend a lot on the number of hashes.
for example, with 2 hashes:
plus 0.07: Speed........: 5013.7M c/s Real, 5085.7M c/s GPU
regular 0.26: Speed.GPU*...: 4035.2M/s
with 100 hashes:
plus 0.07: Speed........: 4581.0M c/s Real, 4884.6M c/s GPU
regular 0.26: Speed.GPU*...: 3968.6M/s
event horizon is somewhere around 1000 hashes.
also, if you take a look at docs/todo.txt it contains this line:
- Should use oclHashcat-lite's candidate generator to lower GPU idle times
once this has been done, it will again boost a lot in speed
|