Wrong Time Estimated with -w 4 parameter - Printable Version +- hashcat Forum (https://hashcat.net/forum) +-- Forum: Support (https://hashcat.net/forum/forum-3.html) +--- Forum: hashcat (https://hashcat.net/forum/forum-45.html) +--- Thread: Wrong Time Estimated with -w 4 parameter (/thread-7767.html) |
Wrong Time Estimated with -w 4 parameter - Nay - 08-26-2018 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 Code: Status...........: Running RE: Wrong Time Estimated with -w 4 parameter - Nay - 09-04-2018 Hi all, No information on this issue/bug ? RE: Wrong Time Estimated with -w 4 parameter - undeath - 09-04-2018 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. RE: Wrong Time Estimated with -w 4 parameter - Nay - 09-04-2018 Thanks for pointing that out, any idea regarding the restore point that doesn't update ? RE: Wrong Time Estimated with -w 4 parameter - atom - 09-08-2018 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. |