Re: [ANN]: cpuminer-opt v3.6.1, open source optimized multi-algo CPU miner
Hello! I have Xeon E5-2678 v3 CPU (12C, 24T, 30M L3 Chache) and i create bat file for hexxcoin:
and i create another bat-file:
How to choose the correct --cpu-affinity option in my case?
Code:
cpuminer-aes-avx2 -a zoin -o stratum+tcp://hexx.suprnova.cc:2876 -u Worker.Rig -p 1979 --cpu-affinity 0x555 --cpu-priority 2
I get 1900H/s.and i create another bat-file:
Code:
cpuminer-aes-avx2 -a zoin -o stratum+tcp://hexx.suprnova.cc:2876 -u Worker.Rig -p 1979 --cpu-affinity 0x8191 --cpu-priority 2
and i get 2100H/s.How to choose the correct --cpu-affinity option in my case?
Using "zoin" algo, you don't need to worry about affinities or priorities. Just create as many threads as you want and let Windows (or Linux) decide the affinities by itself. In your case:
Code:
cpuminer-aes-avx2 -a zoin -t -o stratum+tcp://hexx.suprnova.cc:2876 -u Worker.Rig -p 1979 --cpu-priority 2
Use as any number from 1 to 24.
(I hope joblo agrees with me on this one)
Yes I do.
The issue with zoin (lyra2z330) is memory bandwidth. The CPUs are stalled waiting for memory.
You can reduce the number of threads without losing hash.
An added complication in this case is multi CPU. I'm not sure how logical CPUs are mapped to the individual
Xeons. With a single CPU the default affinity works by assigning one thread to each logical CPU before using
hyperthreading. I don't know whether this will carry to the second CPU. When the first CPU has one thread on
each of it's cores wher does the next thread go? Does it start hyperthreading on the first CPU or start assigning
threads to the second CPU?
You could figure this out by monitoring the CPU's temperatures while running 20 threads with default affinity.
20 threads should be distruibuted evenly accross all 20 physical cores on both Xeons and the temperatures
of the CPUs should be the same. If one is hot and the other cool it indicates the default affinity put 20 threads
on one Xeon. If that happens you will have to play with the affinity to get threads assigned to the second CPU.