06-04-2013, 12:32 AM
(This post was last modified: 06-04-2013, 02:58 AM by Kgx Pnqvhm.)
Watching my taskbar HD LED while hashcat is doing the mangles shows very infrequent writes, so quite a bit of processing is happening between the writes, so I still don't think the I/O involving my HD is the bottleneck.
If it was showing full time writing, I could believe that the HD wasn't keeping up.
UPDATE: Re-trying the same task that took hours the night I first made this post took just minutes, so something must'be been wrong with my system then.
First, I ran mp64.exe to watch how it used system resources. It used less CPU than hashcat, around 10%, but wrote to disk continuously.
Then, I re-ran the same rule & dict combo that I did the other might, that took hours, with very little disk writing.
This time it was writing briefly about once a second, and was using the same 25% CPU like the other night.
And it "felt" as fast as I expected, meaning a brief wait rather than watching a 2 hour movie and going to bed.
I have almost any scheduled task that Windows want to do disabled, so don't know what could have been preventing hashcat from running properly.
If it was showing full time writing, I could believe that the HD wasn't keeping up.
UPDATE: Re-trying the same task that took hours the night I first made this post took just minutes, so something must'be been wrong with my system then.
First, I ran mp64.exe to watch how it used system resources. It used less CPU than hashcat, around 10%, but wrote to disk continuously.
Then, I re-ran the same rule & dict combo that I did the other might, that took hours, with very little disk writing.
This time it was writing briefly about once a second, and was using the same 25% CPU like the other night.
And it "felt" as fast as I expected, meaning a brief wait rather than watching a 2 hour movie and going to bed.
I have almost any scheduled task that Windows want to do disabled, so don't know what could have been preventing hashcat from running properly.