05-20-2023, 05:06 PM
(05-20-2023, 03:27 AM)royce Wrote: Today, the only way to disable autotuning is to manually add your own tuning. On the command line, this is done with -n/--kernel-accel and -u/--kernel-loops. If you do a run, and watch for the accel/loop values that are calculated by autotuning, you can just steal those values and use them and they won't suck.The autotune just set this two values? This is the same for every hash type and GPU? In other words, for the same hash and GPU, for every type of attack I try, the value will be the same? So, can I safety use it "hardcoded"?
(05-20-2023, 03:27 AM)royce Wrote: Side note: if each mask only takes a few seconds to run and you're doing 229k of them, you can probably combine quite a few of them into larger masks.Lol, this was just my first test. And yes, even without autotune, there is the time to start-stop every line. I will need to code a logic to make this more fast
