Quote from: buckya on April 03, 2017, 04:50:14 PM

Hey
At first I'd like to thank You for doing great job, keep up the good work.
I'm currently testing monero mining on FX8320 clocked at 4,1 GHz.
With newest cpuminer-aes-avx.exe i've got better hashrate that with cpuminer-multi.
On 8 threads it goes to 312 H/s on iddle (Win7).
And with only 4 threads tweaked in task manager to use only cores 0, 2, 4 and 6 i got this:

[2017-04-03 18:29:17] CPU #2: 863 H, 58.18 H/s
[2017-04-03 18:29:17] CPU #0: 839 H, 57.07 H/s
[2017-04-03 18:29:17] CPU #1: 844 H, 58.12 H/s
[2017-04-03 18:29:17] CPU #3: 905 H, 60.01 H/s
[2017-04-03 18:29:56] Accepted 38/38 (100%), 4898 H, 232.88 H/s - opened browser with 30+ tabs.
On iddle its going to 248 H/s

I wasn't connecting any power meter but i guess there will be much less power draw on 4 cores.
And here i've got a question about "--cpu-affinity", I don't know how to use it with "--threads 4", so it would direct all work to cores 0, 2, 4, 6 like I'm doing this in Task Manager, but only after launching the .exe
The are some hex parameters which I don't understand like 0xF0F0 or 0x30, I tried use them without effect.
Can You give me some advice ?

I can give you that advice. The --cpu-affinity works as a bit mask. The least significant bit is the core 0, the next one is core 1 and so on.

Imagine the cores like: 0 -- 1 -- 2 -- 3 -- 4 -- 5 -- 6 -- 7 (extended to 7 to fill a BYTE, 8 bits)
Now the bits for each core are: 1 0 1 0 1 0 1 0

This binary value now is encoded with 8th core first, so it becomes => 01010101.

Converting it to hex values (grouping in fours and converting) becomes => 0101 0101 => 0x55

So you must use --cpu-affinity 0x55 in your case.