I tried "-t 12 --cpu-affinity 0x555" (0b010101010101) and got a more high and stable result:
max 2300H/s, avg 2100 H/s on unlocked 2678v3
Topic: [ANN]: cpuminer-opt v3.8.8.1, open source optimized multi-algo CPU miner - page 76. (Read 444067 times)
April 09, 2017, 02:15:16 PM
April 09, 2017, 09:01:42 AM
:: -t 7 + --cpu-affinity 0xffffff= 1712H/s - why?:
I just can not understand the principle of the -cpu-affinity parameter, how does it work?
I just can not understand the principle of the -cpu-affinity parameter, how does it work?
0xffffffff should be the same as the default, some variation in hashrate is expected.
Google affinity mask.
It doesn't seem to be necessary on Intel CPUs, still trying to understand AMD.
April 09, 2017, 05:52:16 AM
i dont know if its an issue or is it my cpu, but ver 3.6.1 always stopped mining after a while, like it stuck after about 30m-1hour mining
I assume there was no error message or you would have mentioned it.
There was an issue reported on one algo where the miner would exit after 50 share submits
if stats were enabled. Stats are disabled by default so this is unlikely.
Most other SW issues would cause an exit much sooner.
Could be CPU or RAM.
yes there are no error message, now im pretty sure its a hardware issue, ive got an error message about ram today when shuting down
April 09, 2017, 04:25:10 AM
If you have one hyperthreaded Intel CPU the default affinity should be correct for any thread count.
Just find the number of threads that gives the best performance.
Affinity should only be a concern with AMD CPUs that have a different way of implementing multicore HW.
As the previous discussions have shown it's still in the learning stage.
Otherwise your calculations are correct.
I tried a different number of threads without cpu-affinity. This gives a worse result than with cpu-affinity. Example:Just find the number of threads that gives the best performance.
Affinity should only be a concern with AMD CPUs that have a different way of implementing multicore HW.
As the previous discussions have shown it's still in the learning stage.
Otherwise your calculations are correct.
Code:
:: c:\Miners\cpuminer-opt-3.6.1-windows\cpuminer-aes-avx2.exe -a zoin -o stratum+tcp://hexx.suprnova.cc:2876 -u spronkin1.Rig1 -p x --cpu-priority 2 -t 1
:: -t 1=478H/s
:: -t 2=660H/s
:: -t 4=1230H/s
:: -t 5=1530H/s
:: -t 6=1470H/s
:: -t 7=1600H/s
:: -t 8=1472H/s
:: -t 9=1423H/s
:: -t 10=1312H/s
:: -t 11=1220H/s
:: -t 12=1210H/s
:: -t 16=1070H/s
:: -t 20=1000H/s
:: -t 23=900H/s
:: -t 7 + --cpu-affinity 0xffffff= 1712H/s - why?:
:: c:\Miners\cpuminer-opt-3.6.1-windows\cpuminer-aes-avx2.exe -a zoin -o stratum+tcp://hexx.suprnova.cc:2876 -u spronkin1.Rig1 -p x --cpu-priority 2 -t 7 --cpu-affinity 0xffffff
:: -t 1=478H/s
:: -t 2=660H/s
:: -t 4=1230H/s
:: -t 5=1530H/s
:: -t 6=1470H/s
:: -t 7=1600H/s
:: -t 8=1472H/s
:: -t 9=1423H/s
:: -t 10=1312H/s
:: -t 11=1220H/s
:: -t 12=1210H/s
:: -t 16=1070H/s
:: -t 20=1000H/s
:: -t 23=900H/s
:: -t 7 + --cpu-affinity 0xffffff= 1712H/s - why?:
:: c:\Miners\cpuminer-opt-3.6.1-windows\cpuminer-aes-avx2.exe -a zoin -o stratum+tcp://hexx.suprnova.cc:2876 -u spronkin1.Rig1 -p x --cpu-priority 2 -t 7 --cpu-affinity 0xffffff
Don't use affinity with default thread count, it just messes things up.
Try different affinities with 12 threads. The default should be the same as 0xffffff.
Code:
:: 0d4095=0b111111111111=0xfff=1230H/s
:: 0d8191=0x1FFF=1240H/s
:: 0d16383=0x3FFF=1240H/s
:: 0d32767=0b111111111111111=0x7FFF=1231H/s
:: 0d33023=0b1000000011111111=0x80FF=1450H/s
:: 0d33151=0b1000000101111111=0x817F=1460H/s
:: 0d33167=0b1000000110001111=0x818F=1763H/s
:: 0d33168=0b1000000110010000=0x8190=1850H/s
:: 0d33169=0b1000000110010001=0x8191=2140H/s
:: 0d33171=0b1000000110010011=0x8193=2200H/s
:: 0d33175=0b1000000110010111=0x8197=2200H/s
:: 0d33199=0bx1000000110101111=0x81AF=1700H/s
:: 0d33279=0b1000000111111111=0x81FF=1430H/s
:: 0d16777215=0b111111111111111111111111=0xffffff=1234H/s (as default affinity)
While I chose this result::: 0d8191=0x1FFF=1240H/s
:: 0d16383=0x3FFF=1240H/s
:: 0d32767=0b111111111111111=0x7FFF=1231H/s
:: 0d33023=0b1000000011111111=0x80FF=1450H/s
:: 0d33151=0b1000000101111111=0x817F=1460H/s
:: 0d33167=0b1000000110001111=0x818F=1763H/s
:: 0d33168=0b1000000110010000=0x8190=1850H/s
:: 0d33169=0b1000000110010001=0x8191=2140H/s
:: 0d33171=0b1000000110010011=0x8193=2200H/s
:: 0d33175=0b1000000110010111=0x8197=2200H/s
:: 0d33199=0bx1000000110101111=0x81AF=1700H/s
:: 0d33279=0b1000000111111111=0x81FF=1430H/s
:: 0d16777215=0b111111111111111111111111=0xffffff=1234H/s (as default affinity)
c:\Miners\cpuminer-opt-3.6.1-windows\cpuminer-aes-avx2.exe -a zoin -o stratum+tcp://hexx.suprnova.cc:2876 -u spronkin1.Rig1 -p x --cpu-priority 2 --cpu-affinity 0x8197
I did not check the hashrate with --cpu-affinity outside this range between 33279 and 65535 or more. I do not know, maybe there are better results. I just can not understand the principle of the -cpu-affinity parameter, how does it work?
April 08, 2017, 01:27:40 PM
The miner can't use what it can't see. It's an OS issue.
OS - win server 2012 r2 see all four NUMA nodes ie 4 phusical CPU, but miner works only with one CPU. What I'm doing wrong?This miner dodn't have even "cpu_threads_configuration" like XMR STAK CPU miner have
How would I know what you're doing wrong if you don't tell me what you're doing?
And if you want to start talking trash, just go away and use STAK.
April 08, 2017, 01:11:33 PM
i dont know if its an issue or is it my cpu, but ver 3.6.1 always stopped mining after a while, like it stuck after about 30m-1hour mining
I assume there was no error message or you would have mentioned it.
There was an issue reported on one algo where the miner would exit after 50 share submits
if stats were enabled. Stats are disabled by default so this is unlikely.
Most other SW issues would cause an exit much sooner.
Could be CPU or RAM.
April 08, 2017, 12:52:05 PM
The miner can't use what it can't see. It's an OS issue.
OS - win server 2012 r2 see all four NUMA nodes ie 4 phusical CPU, but miner works only with one CPU. What I'm doing wrong?This miner dodn't have even "cpu_threads_configuration" like XMR STAK CPU miner have
April 08, 2017, 12:17:26 PM
i dont know if its an issue or is it my cpu, but ver 3.6.1 always stopped mining after a while, like it stuck after about 30m-1hour mining
April 08, 2017, 11:44:07 AM
cpuminer-opt on four socket system don't see more than one phusical CPU.
OS win server 2012 r2
How to run miner on multi socket systems?
OS win server 2012 r2
How to run miner on multi socket systems?
It's the responsibility of the OS to present the available logical CPUs to the applications.
The miner can't use what it can't see. It's an OS issue.
April 08, 2017, 11:18:25 AM
cpuminer-opt on four socket system don't see more than one phusical CPU.
OS win server 2012 r2
How to run miner on multi socket systems?
OS win server 2012 r2
How to run miner on multi socket systems?
April 08, 2017, 09:28:31 AM
What is the default number of threads?
As many as your CPU have them.
April 08, 2017, 08:51:30 AM
What is the default number of threads?
April 07, 2017, 05:45:37 PM
Any chance for large pages support for Windows ?
This was asked before. I won't make any application changes to support huge pages, it's an OS issue.
April 07, 2017, 01:55:08 PM
Any chance for large pages support for Windows ?
April 07, 2017, 09:58:54 AM
sorry for the dumb question, but if i download the files there is no *.exe to start. Where can i find it?
What do you mean by "files"? there is only one zip file to download for Windows.
April 07, 2017, 08:40:12 AM
sorry for the dumb question, but if i download the files there is no *.exe to start. Where can i find it?
What do you mean by "files"? there is only one zip file to download for Windows.
April 07, 2017, 08:37:49 AM
With ryzen 1700 3 ghz vcore 1.125 , with this .bat on hexxcoin have :
cpuminer-aes-avx2 -a lyra2z330 -t 8 --cpu-affinity 0xF0F0 -o stratum+tcp://hexx.suprnova.cc:2876 -u USER -p PASS
[2017-04-07 14:35:13] Accepted 148/148 (100%), 31.93 kH, 649.96 H/s
Its ok ? cpuminer-opt v3.6.1 , Windows 10 x64 .
Power Comsumption is 100 watt and 64 C° with stock air cooler .
cpuminer-aes-avx2 -a lyra2z330 -t 8 --cpu-affinity 0xF0F0 -o stratum+tcp://hexx.suprnova.cc:2876 -u USER -p PASS
[2017-04-07 14:35:13] Accepted 148/148 (100%), 31.93 kH, 649.96 H/s
Its ok ? cpuminer-opt v3.6.1 , Windows 10 x64 .
Power Comsumption is 100 watt and 64 C° with stock air cooler .
That looks pretty good. Is that the configuration that gave you the best performance?
April 07, 2017, 08:03:24 AM
sorry for the dumb question, but if i download the files there is no *.exe to start. Where can i find it?
April 07, 2017, 07:36:28 AM
With ryzen 1700 3 ghz vcore 1.125 , with this .bat on hexxcoin have :
cpuminer-aes-avx2 -a lyra2z330 -t 8 --cpu-affinity 0xF0F0 -o stratum+tcp://hexx.suprnova.cc:2876 -u USER -p PASS
[2017-04-07 14:35:13] Accepted 148/148 (100%), 31.93 kH, 649.96 H/s
Its ok ? cpuminer-opt v3.6.1 , Windows 10 x64 .
Power Comsumption is 100 watt and 64 C° with stock air cooler .
cpuminer-aes-avx2 -a lyra2z330 -t 8 --cpu-affinity 0xF0F0 -o stratum+tcp://hexx.suprnova.cc:2876 -u USER -p PASS
[2017-04-07 14:35:13] Accepted 148/148 (100%), 31.93 kH, 649.96 H/s
Its ok ? cpuminer-opt v3.6.1 , Windows 10 x64 .
Power Comsumption is 100 watt and 64 C° with stock air cooler .
April 07, 2017, 12:51:24 AM
Well, the affinity on Intel CPUs is still worth to try it, especially if u use other apps while mining. E.g. on quad-core CPU with 6Mb L3, affinity (for cpuminer-opt) like --cpu-affinity 14 (cores 1,2,3 and the 0 one is left free) while launching firefox through "START /affinity 1 cmd /C "firefox.exe"" (affine to core 0) keeps hashrate drop like 20h/s while web serfing (firefox is a laggy one), while launching w/o these settings drops hashrate up to 70h/s. Of course, these ones can be done through task manager as well.
Got similar results while using x264, vorbis lancer-sse, lame, mencoder and ffmpeg projects binaries (I'm their real heavy user). Minor changes with image magic and others. It seems that some apps (like firefox) can just slow the whole system w/o actual high cpu usage (can be seen through task manager's "page errors delta"), and manual cpu affinity helps a little bit there.
I've heard about some process threading improvements in Win 8, 8.1 and 10 (I'm currently on 7), but can't be sure.
Got similar results while using x264, vorbis lancer-sse, lame, mencoder and ffmpeg projects binaries (I'm their real heavy user). Minor changes with image magic and others. It seems that some apps (like firefox) can just slow the whole system w/o actual high cpu usage (can be seen through task manager's "page errors delta"), and manual cpu affinity helps a little bit there.
I've heard about some process threading improvements in Win 8, 8.1 and 10 (I'm currently on 7), but can't be sure.
Jump to: