Custom restore points

[sdt]

Thanks @atom @Snoopy for the responses.


Yes, there are a lot of salts - and hashes. 
These are my approx hash stats from the hash files.
approx 2.1M digests , 1.67M unique digests, 1M unique salts

Iam using the same input files ( hashfile) with different modes ( for experiementation )

This is what I observed -
1) when using masked mode ( -a 3 ) ,
- The Restore.points DONOT get incremented . stays at 0 till the end  ( NO restore files are created for the session )

jumps from

Code:

Rejected.........: 0/93317300000 (0.00%)
Restore.Point....: 0/10000 (0.00%)
Restore.Sub.#1...: Salt:933173 Amplifier:0-10 Iteration:0-10
Candidates.#1....: 12345 -> 67646     

                     

to

Code:

Restore.Point....: 10000/10000 (100.00%)

2)  With a dictionary mode ( -a 0 ) with a large dict,
- Restore.points DO get updated  ( but slow )
eg:

Code:

Restore.Point....: 3938534/63941069 (6.16%)

....

Code:

Restore.Point....: 5919896/63941069 (9.26%)

( And the .restore files ARE created )

Am yet to do other experiments .. 
Am not sure if Iam reading too much between the lines when the answer is quite a straight forward 'No - donot expect it '
Just some observations and my effort to save some reruns.

The problem is that you  have too many salts. The more salts, the longer it takes to reach the checkpoint. To verify, try a single (or a few hundret salted hashes), it will reach the checkpoint pretty soon as long as your amplifier (typically rules) are not too many. Also for the large hashlist you have - it will work, it will just take a very very long time. There's no way to change this.