10-28-2020, 08:24 PM
only correct answer: it depends a lot on many factors.
it depends on the hash type, it also depends on the attack type, ...
if you have a slow hash, the H/s (speed in hashes per second) is low, the cracking algo is slow, the GPUs are heavily busy to perform all the iterations or similar (high cost factor).
if you use a dictionary attack without rules (or pipe / stdin, or --slow-candidates run), you need to provide a lot of work to have full acceleration. It's not easy to provide full acceleration if the 4x PCIe slot is the bottleneck.
This means, it depends on where the bottleneck is and if you are able to provide enough work to keep the GPUs busy... for instance, it could be possible to use a "slow transfer" (4x) but still get almost normally high speed and full acceleration by using for instance rules in a dictionary attack (but be aware, that applying rules also increases your total number of password candidates, "keyspace", and this might not be what you want).
it depends on the hash type, it also depends on the attack type, ...
if you have a slow hash, the H/s (speed in hashes per second) is low, the cracking algo is slow, the GPUs are heavily busy to perform all the iterations or similar (high cost factor).
if you use a dictionary attack without rules (or pipe / stdin, or --slow-candidates run), you need to provide a lot of work to have full acceleration. It's not easy to provide full acceleration if the 4x PCIe slot is the bottleneck.
This means, it depends on where the bottleneck is and if you are able to provide enough work to keep the GPUs busy... for instance, it could be possible to use a "slow transfer" (4x) but still get almost normally high speed and full acceleration by using for instance rules in a dictionary attack (but be aware, that applying rules also increases your total number of password candidates, "keyspace", and this might not be what you want).