(10-16-2014, 03:00 PM)philsmd Wrote: 1. there were a lot of changes and atom already mentioned that the default tuning was changed heavily among those versions. Also to avoid users continously reporting freezes, hangs etc
Therefore, you should make sure that the same tuning is used among the versions you test and/or have a look at the parameter:
-w, --workload-profile=NUM Enable a specific workload profile, see references below
The current workload profiles are:
1 = Reduced performance profile (low latency desktop)
2 = Default performance profile
3 = Tuned performance profile (high latency desktop)
So, you should try w/ -w 3, to use the performance profile (instead of the default performance profile, -w 2).
2. pls do not test/benchmark/compare with --force. oclHashcat even warns you that when you use --force you shouldn't ask for help nor report any problems (including performance differences etc). It is also very likely that if you use --force (and the driver is not supported by that specific oclHashcat version), that you miss some cracks etc (and other strange behavior). So pls do not post any more tests w/ --force . Thx
Please notice that '--force' is only used to v1.21, otherwise the program can't start on driver 14.9 !!
Please notice that even run oclexample0.cmd, it turns out the same result. Even I add -w 3, speed is much slower than v1.21 too!
I don't think there was any problem in my tests.