increasing threads for stdout?

[epixoip]

the speed of --stdout has not changed. it helps to actually measure, rather than relying on perception.

0.44 without rules

Code:

epixoip@db:~/hashcat-0.44$ ./hashcat-cli64.bin --stdout ~/wordlists/rockyou.txt | pv -l >/dev/null
14.3M 0:02:57 [80.7k/s]

0.45 without rules

Code:

epixoip@db:~/hashcat-0.45$ ./hashcat-cli64.bin --stdout ~/wordlists/rockyou.txt | pv -l >/dev/null
14.3M 0:02:57 [80.7k/s]

0.44 with rules

Code:

epixoip@db:~/hashcat-0.44$ ./hashcat-cli64.bin --stdout ~/wordlists/top20k.txt -r rules/best64.rule | pv -l >/dev/null
1.66M 0:00:20 [81.1k/s]

0.45 with rules

Code:

epixoip@db:~/hashcat-0.45$ ./hashcat-cli64.bin --stdout ~/wordlists/top20k.txt -r rules/best64.rule | pv -l >/dev/null
1.66M 0:00:20 [81.0k/s]

since you are writing to a file, it would seem that your hard drive or filesystem is the bottleneck here, not hashcat.

also, it could be that the rules that you are testing are un-optimized and slow.