Аccording to your advice I took the example hash, so it's password is known and (I think) the mask and time left doesn't matter yet.
You are right, scrypt is terribly slow.
But, the questions are:
· How much RAM use hashcat for the Ethereum Wallet SCRYPT (15700) hash mode?
· Does it de facto use all available memory from your 256 GB's, although according to your assumption 96 GB (2026 MB (?) per thread * 48 threads) would be enough?
How many threads does hashcat spawn on your system?
In my case 27 (20 of them are engaged in brute force)
It is noticed, that increasing the memory increases the hash rate, but
· what is the optimal RAM volume (in relation to the known number of threads) for the fastest cracking?
You are right, scrypt is terribly slow.
But, the questions are:
· How much RAM use hashcat for the Ethereum Wallet SCRYPT (15700) hash mode?
· Does it de facto use all available memory from your 256 GB's, although according to your assumption 96 GB (2026 MB (?) per thread * 48 threads) would be enough?
How many threads does hashcat spawn on your system?
In my case 27 (20 of them are engaged in brute force)
It is noticed, that increasing the memory increases the hash rate, but
· what is the optimal RAM volume (in relation to the known number of threads) for the fastest cracking?