hashcat Forum › Support › hashcat v
Wrong Time Estimated with -w 4 parameter

Thread Closed 
Threaded Mode
Wrong Time Estimated with -w 4 parameter
Nay Offline
Junior Member
**
Posts: 43
Threads: 9
Joined: Jul 2018
#1
08-26-2018, 11:14 PM
Hello guys,

I've found out that every time I'm using a heavy workload (-w 4) the "Time Estimated" gets longer with time while the Speed doesn't change. A 10h job can reach 15h. Here-below a sample :

As you can see, it goes from ending at 22:28:59 to 23:41:57 while speed stays steady.

Also, restore points never work with -w 4


What could be the reason ?

Code:
Status...........: Running Hash.Type........: vBulletin >= v3.8.5 Hash.Target......: hashes.txt Time.Started.....: Sun Aug 26 18:42:35 2018 (19 mins, 56 secs) Time.Estimated...: Sun Aug 26 22:28:59 2018 (3 hours, 26 mins) [...] Speed.Dev.#2.....: 35891.5 kH/s (254.81ms) Speed.Dev.#3.....: 37634.6 kH/s (166.34ms) Speed.Dev.#*.....: 73484.2 kH/s Recovered........: 6/22 (27.27%) Digests, 6/22 (27.27%) Salts Progress.........: 100923200000/1374263000000 (7.34%) Rejected.........: 0/100923200000 (0.00%) Restore.Point....: 0/250000 (0.00%) [...]


Code:
Status...........: Running Hash.Type........: vBulletin >= v3.8.5 Hash.Target......: hashes.txt Time.Started.....: Sun Aug 26 18:42:35 2018 (3 hours, 56 mins) Time.Estimated...: Sun Aug 26 23:41:57 2018 (1 hour, 2 mins) [...] Speed.Dev.#2.....: 37497.3 kH/s (243.93ms) Speed.Dev.#3.....: 37742.2 kH/s (164.80ms) Speed.Dev.#*.....: 75239.7 kH/s Recovered........: 6/22 (27.27%) Digests, 6/22 (27.27%) Salts Progress.........: 940089000000/1374263000000 (68.41%) Rejected.........: 0/940089000000 (0.00%) Restore.Point....: 0/250000 (0.00%) [...]
Find
Nay Offline
Junior Member
**
Posts: 43
Threads: 9
Joined: Jul 2018
#2
09-04-2018, 02:24 PM
Hi all,

No information on this issue/bug ?
Find
undeath Offline
Sneaky Bastard
******
Posts: 2,293
Threads: 11
Joined: Jul 2010
#3
09-04-2018, 04:20 PM (This post was last modified: 09-04-2018, 04:39 PM by undeath.)
There can be lots of reasons for this. Some other program may have used the GPU within those four hours, leading to a temporary speed drop. Or maybe thermal throttling kicked in, slowing the cards down sometime during the run.
Find
Nay Offline
Junior Member
**
Posts: 43
Threads: 9
Joined: Jul 2018
#4
09-04-2018, 04:41 PM
Thanks for pointing that out, any idea regarding the restore point that doesn't update ?
Find
atom Offline
Administrator
*******
Posts: 5,227
Threads: 233
Joined: Apr 2010
#5
09-08-2018, 10:29 AM
If you use the latest beta, take a look at the salt position and try -S. With enough uncracked salts it might be fast enough to feed your GPUs.
Website Find
Thread Closed