cpuminer-sse2 -a yescrypt -t 32 -o stratum+tcp://pool -u adres -p x --cpu-affinity --cpu-affinity 0x5555555555555555
********** cpuminer-opt 3.7.10 ***********
Start mining with SSE2.
[2018-01-27 10:36:33] Starting Stratum on stratum+tcp://pool
[2018-01-27 10:36:33] 32 miner threads started, using 'yescrypt' algorithm.[0m
[2018-01-27 10:36:34][33m Stratum difficulty set to 0.5[0m
[2018-01-27 10:36:39] CPU #25: 512 H, 318.14 H/s[0m
cpuminer-sse2 -a yescrypt -t 32 -o stratum+tcp://pool -u adres -p x --cpu-affinity --cpu-affinity 0x5555555555555555
********** cpuminer-opt 3.8.0 ***********
Start mining with SSE2.
[2018-01-27 10:37:53][01;30m Binding process to cpu mask 23fcb0[0m
[2018-01-27 10:37:53] Starting Stratum on stratum+tcp://pool
[2018-01-27 10:37:53] 32 miner threads started, using 'yescrypt' algorithm.[0m
[2018-01-27 10:37:55][33m Stratum difficulty set to 0.5[0m
[2018-01-27 10:37:58][36m yescrypt block 64773, diff 0.104[0m
[2018-01-27 10:38:01][01;37m Share submitted.[0m
[2018-01-27 10:38:01] CPU #7: 412 H, 225.37 H/s[0m
[2018-01-27 10:38:01][01;37m [32mAccepted[01;37m 1/1 (100%), diff 1.6e-005, 225.37 H/s[0m
I noticed in version 3.7.10 does not understand the cpu mask
I use the same batch file)
Thank you
Yes it appears to be a problem with cpu-affinity. I made a change in 3.8.0 but it appears it doesn't work.
I'll remove it in the next release and go back to the old way.
When you're testing you can get more info by using --debug, it will give more details about cpu-affinity.
Edit: Why are you using cpu-affinity with 32 threads? Two 6282 SE is 32 cores. With the affinity mask you
used you are only allowing 16 cores to be used for 32 threads.
Don't ever use --cpu-affinity with the same number of threads as cpu cores available, it will only make
things worse.
Please retest v3.7.10 and v3.8.0 with default threads and affinity and with --debug