I've got some free time on the node today so I've tested the -w 3 and messed around with --limit. To be honest it left me with more questions than answers. I've expected that with increasing --limit, I'll get better and better utilization on all 8 GPUs. But that was not the case I ran:
$ hashcat -m 9600 --optimized-kernel-enable --machine-readable -a3 '<office13_example_hash>' ?a?a?a?a?a?a?a?a -s 816687 -l 817568 --status-timer=10 --status --machine-readable -w3
after like 4 minutes since first status shown up I've got
... TEMP 67 70 68 66 69 65 63 64 ... UTIL 64 66 62 69 75 61 61 58
which I've kinda suspected and I'm generally fine with. But, when I've increased --limit to 2 025 419 and ran it like:
$ hashcat -m 9600 --optimized-kernel-enable --machine-readable -a3 '<office13_example_hash>' ?a?a?a?a?a?a?a?a -s 1634255 -l 2025419 --status-timer=10 --status --machine-readable -w 3
after the same time I've got
... TEMP 43 45 43 42 42 44 40 44 ... UTIL 9 9 32 8 8 9 9 17
which makes no sense to me since. Any thoughts or insight?
$ hashcat -m 9600 --optimized-kernel-enable --machine-readable -a3 '<office13_example_hash>' ?a?a?a?a?a?a?a?a -s 816687 -l 817568 --status-timer=10 --status --machine-readable -w3
after like 4 minutes since first status shown up I've got
... TEMP 67 70 68 66 69 65 63 64 ... UTIL 64 66 62 69 75 61 61 58
which I've kinda suspected and I'm generally fine with. But, when I've increased --limit to 2 025 419 and ran it like:
$ hashcat -m 9600 --optimized-kernel-enable --machine-readable -a3 '<office13_example_hash>' ?a?a?a?a?a?a?a?a -s 1634255 -l 2025419 --status-timer=10 --status --machine-readable -w 3
after the same time I've got
... TEMP 43 45 43 42 42 44 40 44 ... UTIL 9 9 32 8 8 9 9 17
which makes no sense to me since. Any thoughts or insight?