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.
Topic: [ANN]: cpuminer-opt v3.8.8.1, open source optimized multi-algo CPU miner - page 77. (Read 444067 times)
April 06, 2017, 03:57:45 PM
April 06, 2017, 02:43:04 PM
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.
I'm sorry if I mis-phrased it. I have 1 CPU Xeon E5v3 (12C, 24T, 30M). The CPU is support Hyperthreading. I just tried to use different bat-files. I do not understand how the start line in the bat file should look to get the maximum hash speed. 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.
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.
Which ones?Try different affinities with 12 threads. The default should be the same as 0xffffff.
12 threads is:
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 8 9 10 11 (extended to 11 to fill a BYTE, 12 bits)
Now the bits for each core are:
1 0 1 0 1 0 1 0 1 0 1 0
This binary value now is encoded with 12th core first, so it becomes =>
010101010101
Converting it to hex values (grouping in fours and converting) becomes => 0101 0101 0101 => 0x555
So i must use --cpu-affinity 0x555 in my case? Or no?
April 06, 2017, 10:59:52 AM
Code:
cpuminer-aes-avx2 -a zoin -o stratum+tcp://hexx.suprnova.cc:2876 -u Worker.Rig -p 1979 --cpu-priority 2 -t 23
Code:
cpuminer-aes-avx2 -a zoin -o stratum+tcp://hexx.suprnova.cc:2876 -u Worker.Rig -p 1979 --cpu-affinity 4095 --cpu-priority 2
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.
April 06, 2017, 10:41:42 AM
I have two socket motherboard and two xeon 2630 v4, on windows i see 8 cores mostly idling (32 cores fully loaded)
dedondesta, cpuminer might have a maximum of 32 threads. joblo would know better then I. If that's the case then perhaps run two instances and map each one to it's own socket.There is no coded limit on the number of threads, the physical limit is sizeof int.
It's not clear what happens when there are more threads than CPUs.
Running 2 instances may be an alternative if affinity can't be set correctly with one instance.
April 06, 2017, 10:28:59 AM
Hello! I have Xeon E5-2678 v3 CPU (12C, 24T, 30M L3 Chache) and i create bat file for hexxcoin:
I get 1900H/s.
and i create another bat-file:
and i get 2100H/s.
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
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
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
(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.
April 06, 2017, 09:29:27 AM
Hello! I have Xeon E5-2678 v3 CPU (12C, 24T, 30M L3 Chache) and i create bat file for hexxcoin:
I get 1900H/s.
and i create another bat-file:
and i get 2100H/s.
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
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
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
(I hope joblo agrees with me on this one)
Code:
cpuminer-aes-avx2 -a zoin -o stratum+tcp://hexx.suprnova.cc:2876 -u Worker.Rig -p 1979 --cpu-priority 2 -t 23
Code:
cpuminer-aes-avx2 -a zoin -o stratum+tcp://hexx.suprnova.cc:2876 -u Worker.Rig -p 1979 --cpu-affinity 4095 --cpu-priority 2
April 06, 2017, 08:43:58 AM
I have two socket motherboard and two xeon 2630 v4, on windows i see 8 cores mostly idling (32 cores fully loaded)
dedondesta, cpuminer might have a maximum of 32 threads. joblo would know better then I. If that's the case then perhaps run two instances and map each one to it's own socket. April 06, 2017, 08:03:02 AM
Hello! I have Xeon E5-2678 v3 CPU (12C, 24T, 30M L3 Chache) and i create bat file for hexxcoin:
I get 1900H/s.
and i create another bat-file:
and i get 2100H/s.
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
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
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
(I hope joblo agrees with me on this one)
April 06, 2017, 07:46:31 AM
Hello! I have Xeon E5-2678 v3 CPU (12C, 24T, 30M L3 Chache) and i create bat file for hexxcoin:
I get 1900H/s.
and i create another bat-file:
and i get 2100H/s.
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
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
How to choose the correct --cpu-affinity option in my case?
April 06, 2017, 02:29:20 AM
Is best intel i7 7700k or amd ryzen 1700 for mining monero and hexxcoin ? .
April 05, 2017, 11:11:07 PM
I have two socket motherboard and two xeon 2630 v4, on windows i see 8 cores mostly idling (32 cores fully loaded)
this is how i run it
cpuminer-aes-avx2 -a zoin -o stratum+tcp://xxx:xxxx -u xxxx.xxxx -p xxxx --cpu-priority 0
should i set --cpu-affinity to certain value to make use all the cores?
right now having this performance
Also, i see that i have CPU #39 above
but take a look at my cpu load
https://s2.postimg.org/6aaf8ttm1/iii.png
this is how i run it
cpuminer-aes-avx2 -a zoin -o stratum+tcp://xxx:xxxx -u xxxx.xxxx -p xxxx --cpu-priority 0
should i set --cpu-affinity to certain value to make use all the cores?
right now having this performance
Code:
2017-04-06 08:25:07] Accepted 68/69 (98.6%), 68.36 kH, 1255.98 H/s
2017-04-06 08:25:12] CPU #6: 166 H, 14.49 H/s
2017-04-06 08:25:13] Accepted 69/70 (98.6%), 67.65 kH, 1255.89 H/s
2017-04-06 08:25:17] CPU #28: 3339 H, 55.74 H/s
2017-04-06 08:25:21] CPU #23: 3352 H, 55.86 H/s
2017-04-06 08:25:22] CPU #28: 237 H, 55.57 H/s
2017-04-06 08:25:22] CPU #38: 876 H, 14.58 H/s
2017-04-06 08:25:22] Accepted 70/71 (98.6%), 67.09 kH, 1255.80 H/s
2017-04-06 08:25:26] CPU #8: 1766 H, 29.41 H/s
2017-04-06 08:25:30] CPU #27: 3349 H, 55.85 H/s
2017-04-06 08:25:33] CPU #21: 3350 H, 55.91 H/s
2017-04-06 08:25:33] CPU #25: 2706 H, 55.89 H/s
2017-04-06 08:25:33] Accepted 71/72 (98.6%), 68.28 kH, 1255.89 H/s
2017-04-06 08:25:34] CPU #37: 874 H, 14.57 H/s
2017-04-06 08:25:36] CPU #10: 1788 H, 29.77 H/s
2017-04-06 08:25:36] CPU #39: 871 H, 14.57 H/s
2017-04-06 08:25:43] CPU #8: 522 H, 29.34 H/s
2017-04-06 08:25:44] Accepted 72/73 (98.6%), 67.63 kH, 1255.87 H/s
2017-04-06 08:25:47] CPU #11: 1788 H, 29.77 H/s
2017-04-06 08:25:54] CPU #17: 1763 H, 29.36 H/s
2017-04-06 08:25:59] CPU #24: 3107 H, 55.86 H/s
2017-04-06 08:25:59] Accepted 73/74 (98.6%), 67.39 kH, 1255.86 H/s
Also, i see that i have CPU #39 above
but take a look at my cpu load
https://s2.postimg.org/6aaf8ttm1/iii.png
April 05, 2017, 11:07:48 PM
Good data. Using alternate cores gives 5 kH/s less than single threaded. This looks like it
may be the best if turbo boost (AMD's version) is taken into consideration. You can confirm
the system is balanced by comparing the temperature of the cores. They should all be close
to the same temp. If any are hotter or cooler in indicates a core that is running 2 threads or no
threads.
may be the best if turbo boost (AMD's version) is taken into consideration. You can confirm
the system is balanced by comparing the temperature of the cores. They should all be close
to the same temp. If any are hotter or cooler in indicates a core that is running 2 threads or no
threads.
April 05, 2017, 06:43:31 PM
Code:
----- 0x0F0F -----
********** cpuminer-opt 3.6.1 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
Forked from TPruvot's cpuminer-multi with credits
to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
Wolf0, Jeff Garzik and Optiminer.
CPU: AMD Ryzen 7 1800X Eight-Core Processor
CPU features: SSE2 AES AVX AVX2 SHA
SW built on Mar 31 2017 with GCC 4.8.3
SW features: SSE2 AES AVX AVX2
Algo features: SSE2 AES
Start mining with SSE2 AES
[2017-04-05 18:21:33][01;30m Binding process to cpu mask f0f[0m
[2017-04-05 18:21:33] Starting Stratum on stratum+tcp://xmr-usa.dwarfpool.com:8005[0m
[2017-04-05 18:21:33][01;30m Binding thread 2 to cpu mask f0f[0m
[2017-04-05 18:21:33] 8 miner threads started, using 'cryptonight' algorithm.[0m
[2017-04-05 18:21:33][01;30m Binding thread 6 to cpu mask f0f[0m
[2017-04-05 18:21:33][01;30m Binding thread 0 to cpu mask f0f[0m
[2017-04-05 18:21:33][01;30m Binding thread 4 to cpu mask f0f[0m
[2017-04-05 18:21:33][01;30m Binding thread 5 to cpu mask f0f[0m
[2017-04-05 18:21:33][01;30m Binding thread 3 to cpu mask f0f[0m
[2017-04-05 18:21:33][01;30m Binding thread 1 to cpu mask f0f[0m
[2017-04-05 18:21:33][01;30m Binding thread 7 to cpu mask f0f[0m
[2017-04-05 18:21:33][01;30m Auth id: 821619354607537[0m
[2017-04-05 18:21:33][33m Stratum difficulty set to 10000[0m
[2017-04-05 18:21:36] CPU #6: 66 H, 35.98 H/s[0m
[2017-04-05 18:21:36] CPU #3: 66 H, 35.42 H/s[0m
[2017-04-05 18:21:36] CPU #5: 66 H, 34.63 H/s[0m
[2017-04-05 18:21:36] CPU #7: 66 H, 34.28 H/s[0m
[2017-04-05 18:21:36] CPU #2: 66 H, 33.87 H/s[0m
[2017-04-05 18:21:36] CPU #4: 66 H, 33.65 H/s[0m
[2017-04-05 18:21:36] CPU #0: 66 H, 30.72 H/s[0m
[2017-04-05 18:21:36] CPU #1: 66 H, 28.41 H/s[0m
[2017-04-05 18:21:51] CPU #2: 568 H, 36.52 H/s[0m
[2017-04-05 18:21:52][01;37m [32mAccepted[01;37m 1/1 (100%), 1030 H, 269.61 H/s[0m
[2017-04-05 18:22:08] CPU #0: 1070 H, 33.81 H/s[0m
[2017-04-05 18:22:08][01;37m [32mAccepted[01;37m 2/2 (100%), 2034 H, 272.70 H/s[0m
[2017-04-05 18:22:29] CPU #1: 1706 H, 32.48 H/s[0m
[2017-04-05 18:22:30] CPU #4: 2021 H, 37.34 H/s[0m
[2017-04-05 18:22:30] CPU #3: 2126 H, 39.15 H/s[0m
[2017-04-05 18:22:30] CPU #7: 2058 H, 37.71 H/s[0m
[2017-04-05 18:22:31] CPU #5: 2079 H, 37.71 H/s[0m
[2017-04-05 18:22:31] CPU #6: 2160 H, 38.69 H/s[0m
[2017-04-05 18:22:36] CPU #0: 1026 H, 36.43 H/s[0m
[2017-04-05 18:22:36][01;37m [32mAccepted[01;37m 3/3 (100%), 13.74 kH, 296.03 H/s[0m
[2017-04-05 18:22:50] CPU #2: 2193 H, 37.69 H/s[0m
[2017-04-05 18:23:14] CPU #3: 1517 H, 34.38 H/s[0m
[2017-04-05 18:23:14][01;37m [32mAccepted[01;37m 4/4 (100%), 14.76 kH, 292.43 H/s[0m
[2017-04-05 18:23:14] CPU #4: 1656 H, 37.24 H/s[0m
[2017-04-05 18:23:15][01;37m [32mAccepted[01;37m 5/5 (100%), 14.40 kH, 292.33 H/s[0m
[2017-04-05 18:23:21] CPU #1: 1950 H, 36.93 H/s[0m
[2017-04-05 18:23:30] CPU #5: 2264 H, 38.01 H/s[0m
[2017-04-05 18:23:31] CPU #7: 2264 H, 37.51 H/s[0m
[2017-04-05 18:23:33] CPU #0: 2188 H, 37.96 H/s[0m
[2017-04-05 18:23:36] CPU #6: 2323 H, 36.04 H/s[0m
[2017-04-05 18:23:49] CPU #2: 2263 H, 38.00 H/s[0m
[2017-04-05 18:23:50] CPU #2: 22 H, 36.75 H/s[0m
[2017-04-05 18:23:50][01;37m [32mAccepted[01;37m 6/6 (100%), 14.18 kH, 294.81 H/s[0m
[2017-04-05 18:24:05] CPU #4: 1906 H, 37.74 H/s[0m
[2017-04-05 18:24:05] CPU #6: 1010 H, 34.91 H/s[0m
[2017-04-05 18:24:05] CPU #5: 1304 H, 37.84 H/s[0m
[2017-04-05 18:24:05] CPU #1: 1667 H, 38.40 H/s[0m
[2017-04-05 18:24:05] CPU #3: 1805 H, 35.54 H/s[0m
[2017-04-05 18:24:05] CPU #7: 1293 H, 37.78 H/s[0m
[2017-04-05 18:24:05] CPU #0: 1061 H, 33.70 H/s[0m
[2017-04-05 18:24:05] CPU #2: 567 H, 37.20 H/s[0m
[2017-04-05 18:24:59] CPU #3: 2134 H, 39.53 H/s[0m
[2017-04-05 18:25:03] CPU #2: 2234 H, 38.20 H/s[0m
[2017-04-05 18:25:04] CPU #4: 2266 H, 38.20 H/s[0m
[2017-04-05 18:25:04] CPU #7: 2268 H, 38.20 H/s[0m
[2017-04-05 18:25:04] CPU #5: 2272 H, 38.20 H/s[0m
[2017-04-05 18:25:05] CPU #1: 2306 H, 38.62 H/s[0m
[2017-04-05 18:25:05] CPU #6: 2096 H, 34.82 H/s[0m
[2017-04-05 18:25:06] CPU #0: 2024 H, 33.28 H/s[0m
[2017-04-05 18:25:56] CPU #5: 1977 H, 38.22 H/s[0m
[2017-04-05 18:25:56][01;37m [32mAccepted[01;37m 7/7 (100%), 17.31 kH, 299.06 H/s[0m
[2017-04-05 18:26:00] CPU #6: 2091 H, 38.06 H/s[0m
[2017-04-05 18:26:01] CPU #0: 1998 H, 36.25 H/s[0m
[2017-04-05 18:26:01] CPU #3: 2373 H, 38.17 H/s[0m
[2017-04-05 18:26:04] CPU #2: 2294 H, 38.11 H/s[0m
[2017-04-05 18:26:04] CPU #7: 2293 H, 38.20 H/s[0m
[2017-04-05 18:26:04] CPU #4: 2294 H, 38.09 H/s[0m
[2017-04-05 18:26:12] CPU #1: 2318 H, 34.30 H/s[0m
----- 0xF0F0 -----
********** cpuminer-opt 3.6.1 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
Forked from TPruvot's cpuminer-multi with credits
to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
Wolf0, Jeff Garzik and Optiminer.
CPU: AMD Ryzen 7 1800X Eight-Core Processor
CPU features: SSE2 AES AVX AVX2 SHA
SW built on Mar 31 2017 with GCC 4.8.3
SW features: SSE2 AES AVX AVX2
Algo features: SSE2 AES
Start mining with SSE2 AES
[2017-04-05 18:26:41][01;30m Binding process to cpu mask f0f0[0m
[2017-04-05 18:26:41] Starting Stratum on stratum+tcp://xmr-usa.dwarfpool.com:8005[0m
[2017-04-05 18:26:41][01;30m Binding thread 0 to cpu mask f0f0[0m
[2017-04-05 18:26:41][01;30m Binding thread 1 to cpu mask f0f0[0m
[2017-04-05 18:26:41] 8 miner threads started, using 'cryptonight' algorithm.[0m
[2017-04-05 18:26:41][01;30m Binding thread 6 to cpu mask f0f0[0m
[2017-04-05 18:26:41][01;30m Binding thread 3 to cpu mask f0f0[0m
[2017-04-05 18:26:41][01;30m Binding thread 5 to cpu mask f0f0[0m
[2017-04-05 18:26:41][01;30m Binding thread 2 to cpu mask f0f0[0m
[2017-04-05 18:26:41][01;30m Binding thread 7 to cpu mask f0f0[0m
[2017-04-05 18:26:41][01;30m Binding thread 4 to cpu mask f0f0[0m
[2017-04-05 18:26:41][01;30m Auth id: 750266114971600[0m
[2017-04-05 18:26:41][33m Stratum difficulty set to 10000[0m
[2017-04-05 18:26:44] CPU #2: 66 H, 37.92 H/s[0m
[2017-04-05 18:26:44] CPU #0: 66 H, 37.56 H/s[0m
[2017-04-05 18:26:44] CPU #7: 66 H, 37.48 H/s[0m
[2017-04-05 18:26:44] CPU #3: 66 H, 37.39 H/s[0m
[2017-04-05 18:26:44] CPU #6: 66 H, 37.10 H/s[0m
[2017-04-05 18:26:44] CPU #4: 66 H, 37.09 H/s[0m
[2017-04-05 18:26:44] CPU #5: 66 H, 35.52 H/s[0m
[2017-04-05 18:26:44] CPU #1: 66 H, 35.42 H/s[0m
[2017-04-05 18:27:32] CPU #5: 1733 H, 35.63 H/s[0m
[2017-04-05 18:27:32][01;37m [32mAccepted[01;37m 1/1 (100%), 2195 H, 295.60 H/s[0m
[2017-04-05 18:27:43] CPU #3: 2245 H, 37.98 H/s[0m
[2017-04-05 18:27:43] CPU #7: 2250 H, 37.99 H/s[0m
[2017-04-05 18:27:43] CPU #0: 2255 H, 37.98 H/s[0m
[2017-04-05 18:27:43] CPU #4: 2227 H, 37.33 H/s[0m
[2017-04-05 18:27:43] CPU #6: 2227 H, 37.30 H/s[0m
[2017-04-05 18:27:43] CPU #1: 2127 H, 35.62 H/s[0m
[2017-04-05 18:27:43] CPU #2: 2277 H, 38.00 H/s[0m
[2017-04-05 18:27:47] CPU #2: 126 H, 37.82 H/s[0m
[2017-04-05 18:27:47][01;37m [32mAccepted[01;37m 2/2 (100%), 15.19 kH, 297.64 H/s[0m
[2017-04-05 18:28:31] CPU #4: 1787 H, 37.62 H/s[0m
[2017-04-05 18:28:31] CPU #0: 1807 H, 37.80 H/s[0m
[2017-04-05 18:28:31] CPU #1: 1747 H, 36.87 H/s[0m
[2017-04-05 18:28:31] CPU #3: 1817 H, 37.80 H/s[0m
[2017-04-05 18:28:31] CPU #7: 1813 H, 37.80 H/s[0m
[2017-04-05 18:28:31] CPU #2: 1662 H, 37.80 H/s[0m
[2017-04-05 18:28:31] CPU #5: 2087 H, 35.70 H/s[0m
[2017-04-05 18:28:31] CPU #6: 1701 H, 35.83 H/s[0m
[2017-04-05 18:28:40] CPU #3: 338 H, 37.67 H/s[0m
[2017-04-05 18:28:40][01;37m [32mAccepted[01;37m 3/3 (100%), 12.94 kH, 297.09 H/s[0m
[2017-04-05 18:29:00] CPU #1: 1035 H, 35.97 H/s[0m
[2017-04-05 18:29:00][01;37m [32mAccepted[01;37m 4/4 (100%), 12.23 kH, 296.18 H/s[0m
[2017-04-05 18:29:05] CPU #6: 1249 H, 36.62 H/s[0m
[2017-04-05 18:29:05][01;37m [32mAccepted[01;37m 5/5 (100%), 11.78 kH, 296.98 H/s[0m
[2017-04-05 18:29:13] CPU #4: 1589 H, 37.39 H/s[0m
[2017-04-05 18:29:13][01;37m [32mAccepted[01;37m 6/6 (100%), 11.58 kH, 296.74 H/s[0m
[2017-04-05 18:29:31] CPU #2: 2270 H, 37.87 H/s[0m
[2017-04-05 18:29:31] CPU #0: 2269 H, 37.83 H/s[0m
[2017-04-05 18:29:31] CPU #7: 2269 H, 37.82 H/s[0m
[2017-04-05 18:29:31] CPU #5: 2143 H, 35.55 H/s[0m
[2017-04-05 18:29:39] CPU #3: 2262 H, 37.87 H/s[0m
[2017-04-05 18:29:43] CPU #1: 1555 H, 35.87 H/s[0m
[2017-04-05 18:29:43][01;37m [32mAccepted[01;37m 7/7 (100%), 15.61 kH, 296.82 H/s[0m
[2017-04-05 18:29:50] CPU #3: 399 H, 37.97 H/s[0m
[2017-04-05 18:29:50][01;37m [32mAccepted[01;37m 8/8 (100%), 13.74 kH, 296.92 H/s[0m
[2017-04-05 18:30:01] CPU #7: 1156 H, 37.98 H/s[0m
[2017-04-05 18:30:01] CPU #1: 650 H, 35.50 H/s[0m
[2017-04-05 18:30:01] CPU #6: 2086 H, 37.05 H/s[0m
[2017-04-05 18:30:01] CPU #3: 427 H, 38.06 H/s[0m
[2017-04-05 18:30:01] CPU #4: 1790 H, 37.35 H/s[0m
[2017-04-05 18:30:01] CPU #0: 1157 H, 37.98 H/s[0m
[2017-04-05 18:30:01] CPU #2: 1158 H, 37.98 H/s[0m
[2017-04-05 18:30:01] CPU #5: 1071 H, 35.51 H/s[0m
[2017-04-05 18:30:02] CPU #2: 20 H, 37.81 H/s[0m
[2017-04-05 18:30:02][01;37m [32mAccepted[01;37m 9/9 (100%), 8357 H, 297.23 H/s[0m
[2017-04-05 18:30:40] CPU #3: 1339 H, 34.22 H/s[0m
[2017-04-05 18:30:40][01;37m [32mAccepted[01;37m 10/10 (100%), 9269 H, 293.39 H/s[0m
[2017-04-05 18:30:52] CPU #7: 1781 H, 34.97 H/s[0m
[2017-04-05 18:30:52][01;37m [32mAccepted[01;37m 11/11 (100%), 9894 H, 290.38 H/s[0m
[2017-04-05 18:31:04] CPU #5: 2132 H, 33.73 H/s[0m
[2017-04-05 18:31:05] CPU #1: 2132 H, 33.60 H/s[0m
[2017-04-05 18:31:05] CPU #4: 2243 H, 34.98 H/s[0m
[2017-04-05 18:31:05] CPU #0: 2280 H, 35.54 H/s[0m
[2017-04-05 18:31:05] CPU #2: 2270 H, 35.63 H/s[0m
[2017-04-05 18:31:06] CPU #6: 2224 H, 34.25 H/s[0m
[2017-04-05 18:31:35] CPU #3: 2055 H, 37.80 H/s[0m
[2017-04-05 18:31:39] CPU #6: 1220 H, 37.37 H/s[0m
[2017-04-05 18:31:39][01;37m [32mAccepted[01;37m 12/12 (100%), 16.11 kH, 283.61 H/s[0m
----- 0x5555 -----
********** cpuminer-opt 3.6.1 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
Forked from TPruvot's cpuminer-multi with credits
to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
Wolf0, Jeff Garzik and Optiminer.
CPU: AMD Ryzen 7 1800X Eight-Core Processor
CPU features: SSE2 AES AVX AVX2 SHA
SW built on Mar 31 2017 with GCC 4.8.3
SW features: SSE2 AES AVX AVX2
Algo features: SSE2 AES
Start mining with SSE2 AES
[2017-04-05 18:31:41][01;30m Binding process to cpu mask 5555[0m
[2017-04-05 18:31:41] Starting Stratum on stratum+tcp://xmr-usa.dwarfpool.com:8005[0m
[2017-04-05 18:31:41][01;30m Binding thread 0 to cpu mask 5555[0m
[2017-04-05 18:31:41][01;30m Binding thread 4 to cpu mask 5555[0m
[2017-04-05 18:31:41][01;30m Binding thread 5 to cpu mask 5555[0m
[2017-04-05 18:31:41] 8 miner threads started, using 'cryptonight' algorithm.[0m
[2017-04-05 18:31:41][01;30m Binding thread 3 to cpu mask 5555[0m
[2017-04-05 18:31:41][01;30m Binding thread 7 to cpu mask 5555[0m
[2017-04-05 18:31:41][01;30m Binding thread 2 to cpu mask 5555[0m
[2017-04-05 18:31:41][01;30m Binding thread 6 to cpu mask 5555[0m
[2017-04-05 18:31:41][01;30m Binding thread 1 to cpu mask 5555[0m
[2017-04-05 18:31:41][01;30m Auth id: 714213534840382[0m
[2017-04-05 18:31:41][33m Stratum difficulty set to 10000[0m
[2017-04-05 18:31:43] CPU #0: 66 H, 51.93 H/s[0m
[2017-04-05 18:31:43] CPU #1: 66 H, 51.85 H/s[0m
[2017-04-05 18:31:43] CPU #7: 66 H, 51.56 H/s[0m
[2017-04-05 18:31:43] CPU #6: 66 H, 51.38 H/s[0m
[2017-04-05 18:31:43] CPU #2: 66 H, 51.24 H/s[0m
[2017-04-05 18:31:43] CPU #5: 66 H, 50.73 H/s[0m
[2017-04-05 18:31:43] CPU #3: 66 H, 50.61 H/s[0m
[2017-04-05 18:31:43] CPU #4: 66 H, 46.42 H/s[0m
[2017-04-05 18:31:56] CPU #6: 651 H, 51.57 H/s[0m
[2017-04-05 18:31:56] CPU #4: 576 H, 46.13 H/s[0m
[2017-04-05 18:31:56] CPU #2: 643 H, 50.94 H/s[0m
[2017-04-05 18:31:56] CPU #1: 651 H, 51.51 H/s[0m
[2017-04-05 18:31:56] CPU #5: 640 H, 50.74 H/s[0m
[2017-04-05 18:31:56] CPU #7: 650 H, 51.44 H/s[0m
[2017-04-05 18:31:56] CPU #3: 643 H, 50.98 H/s[0m
[2017-04-05 18:31:56] CPU #0: 652 H, 51.56 H/s[0m
[2017-04-05 18:32:10] CPU #0: 751 H, 51.56 H/s[0m
[2017-04-05 18:32:10][01;37m [32mAccepted[01;37m 1/1 (100%), 5205 H, 404.86 H/s[0m
[2017-04-05 18:32:40] CPU #1: 2279 H, 51.56 H/s[0m
[2017-04-05 18:32:40][01;37m [32mAccepted[01;37m 2/2 (100%), 6833 H, 404.92 H/s[0m
[2017-04-05 18:32:56] CPU #7: 3088 H, 51.56 H/s[0m
[2017-04-05 18:32:56] CPU #3: 3060 H, 50.98 H/s[0m
[2017-04-05 18:32:56] CPU #2: 3058 H, 50.94 H/s[0m
[2017-04-05 18:32:56] CPU #5: 3046 H, 50.72 H/s[0m
[2017-04-05 18:32:56] CPU #6: 3096 H, 51.54 H/s[0m
[2017-04-05 18:32:56] CPU #4: 2769 H, 46.00 H/s[0m
[2017-04-05 18:33:10] CPU #0: 3095 H, 51.62 H/s[0m
[2017-04-05 18:33:15] CPU #3: 963 H, 51.03 H/s[0m
[2017-04-05 18:33:15] CPU #4: 862 H, 46.07 H/s[0m
[2017-04-05 18:33:15] CPU #5: 955 H, 50.69 H/s[0m
[2017-04-05 18:33:15] CPU #2: 963 H, 51.03 H/s[0m
[2017-04-05 18:33:15] CPU #7: 980 H, 51.55 H/s[0m
[2017-04-05 18:33:15] CPU #0: 225 H, 51.39 H/s[0m
[2017-04-05 18:33:15] CPU #6: 971 H, 51.52 H/s[0m
[2017-04-05 18:33:15] CPU #1: 1793 H, 51.65 H/s[0m
[2017-04-05 18:33:18] CPU #6: 163 H, 51.82 H/s[0m
[2017-04-05 18:33:18][01;37m [32mAccepted[01;37m 3/3 (100%), 6904 H, 405.21 H/s[0m
[2017-04-05 18:33:19] CPU #0: 215 H, 51.42 H/s[0m
[2017-04-05 18:33:19][01;37m [32mAccepted[01;37m 4/4 (100%), 6894 H, 405.24 H/s[0m
[2017-04-05 18:34:15] CPU #5: 3043 H, 50.62 H/s[0m
[2017-04-05 18:34:15] CPU #7: 3094 H, 51.43 H/s[0m
[2017-04-05 18:34:15] CPU #3: 3063 H, 50.89 H/s[0m
[2017-04-05 18:34:15] CPU #1: 3100 H, 51.50 H/s[0m
[2017-04-05 18:34:15] CPU #2: 3063 H, 50.84 H/s[0m
[2017-04-05 18:34:15] CPU #4: 2766 H, 45.87 H/s[0m
[2017-04-05 18:34:18] CPU #6: 3111 H, 51.44 H/s[0m
[2017-04-05 18:34:19] CPU #0: 3087 H, 51.51 H/s[0m
[2017-04-05 18:34:24] CPU #5: 477 H, 50.82 H/s[0m
[2017-04-05 18:34:24][01;37m [32mAccepted[01;37m 5/5 (100%), 21.76 kH, 404.30 H/s[0m
[2017-04-05 18:34:29] CPU #5: 235 H, 50.85 H/s[0m
[2017-04-05 18:34:29][01;37m [32mAccepted[01;37m 6/6 (100%), 21.52 kH, 404.33 H/s[0m
[2017-04-05 18:34:41] CPU #5: 639 H, 50.75 H/s[0m
[2017-04-05 18:34:41][01;37m [32mAccepted[01;37m 7/7 (100%), 21.92 kH, 404.23 H/s[0m
[2017-04-05 18:34:57] CPU #5: 798 H, 50.83 H/s[0m
[2017-04-05 18:34:57][01;37m [32mAccepted[01;37m 8/8 (100%), 22.08 kH, 404.30 H/s[0m
[2017-04-05 18:35:10] CPU #2: 2832 H, 50.96 H/s[0m
[2017-04-05 18:35:10][01;37m [32mAccepted[01;37m 9/9 (100%), 21.85 kH, 404.43 H/s[0m
[2017-04-05 18:35:15] CPU #3: 3055 H, 51.04 H/s[0m
[2017-04-05 18:35:15] CPU #4: 2754 H, 46.04 H/s[0m
[2017-04-05 18:35:15] CPU #7: 3088 H, 51.45 H/s[0m
[2017-04-05 18:35:15] CPU #1: 3091 H, 51.53 H/s[0m
[2017-04-05 18:35:18] CPU #6: 3088 H, 51.60 H/s[0m
[2017-04-05 18:35:19] CPU #0: 3092 H, 51.53 H/s[0m
[2017-04-05 18:35:37] CPU #1: 1147 H, 51.62 H/s[0m
[2017-04-05 18:35:37][01;37m [32mAccepted[01;37m 10/10 (100%), 19.85 kH, 405.06 H/s[0m
[2017-04-05 18:35:53] CPU #7: 1953 H, 51.56 H/s[0m
[2017-04-05 18:35:53] CPU #3: 1937 H, 50.94 H/s[0m
[2017-04-05 18:35:53] CPU #0: 1751 H, 51.59 H/s[0m
[2017-04-05 18:35:53] CPU #1: 807 H, 51.56 H/s[0m
[2017-04-05 18:35:53] CPU #4: 1751 H, 46.13 H/s[0m
[2017-04-05 18:35:53] CPU #6: 1784 H, 51.59 H/s[0m
[2017-04-05 18:35:53] CPU #2: 2154 H, 50.99 H/s[0m
[2017-04-05 18:35:53] CPU #5: 2824 H, 50.74 H/s[0m
[2017-04-05 18:35:54] CPU #6: 81 H, 51.88 H/s[0m
[2017-04-05 18:35:54][01;37m [32mAccepted[01;37m 11/11 (100%), 13.26 kH, 405.40 H/s[0m
[2017-04-05 18:36:08] CPU #6: 682 H, 50.78 H/s[0m
[2017-04-05 18:36:08][01;37m [32mAccepted[01;37m 12/12 (100%), 13.86 kH, 404.29 H/s[0m
[2017-04-05 18:36:31] CPU #5: 1879 H, 49.21 H/s[0m
[2017-04-05 18:36:31][01;37m [32mAccepted[01;37m 13/13 (100%), 12.91 kH, 402.76 H/s[0m
[2017-04-05 18:36:31] CPU #2: 1914 H, 49.67 H/s[0m
[2017-04-05 18:36:31][01;37m [32mAccepted[01;37m 14/14 (100%), 12.67 kH, 401.43 H/s[0m
[2017-04-05 18:36:35] CPU #3: 2063 H, 48.89 H/s[0m
[2017-04-05 18:36:35][01;37m [32mAccepted[01;37m 15/15 (100%), 12.80 kH, 399.38 H/s[0m
----- 0xAAAA -----
********** cpuminer-opt 3.6.1 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
Forked from TPruvot's cpuminer-multi with credits
to Lucas Jones, elmad, palmd, djm34, pooler, ig0tik3d,
Wolf0, Jeff Garzik and Optiminer.
CPU: AMD Ryzen 7 1800X Eight-Core Processor
CPU features: SSE2 AES AVX AVX2 SHA
SW built on Mar 31 2017 with GCC 4.8.3
SW features: SSE2 AES AVX AVX2
Algo features: SSE2 AES
Start mining with SSE2 AES
[2017-04-05 18:36:41][01;30m Binding process to cpu mask aaaa[0m
[2017-04-05 18:36:41] Starting Stratum on stratum+tcp://xmr-usa.dwarfpool.com:8005[0m
[2017-04-05 18:36:41][01;30m Binding thread 0 to cpu mask aaaa[0m
[2017-04-05 18:36:41][01;30m Binding thread 3 to cpu mask aaaa[0m
[2017-04-05 18:36:41][01;30m Binding thread 4 to cpu mask aaaa[0m
[2017-04-05 18:36:41][01;30m Binding thread 1 to cpu mask aaaa[0m
[2017-04-05 18:36:41] 8 miner threads started, using 'cryptonight' algorithm.[0m
[2017-04-05 18:36:41][01;30m Binding thread 2 to cpu mask aaaa[0m
[2017-04-05 18:36:41][01;30m Binding thread 5 to cpu mask aaaa[0m
[2017-04-05 18:36:41][01;30m Binding thread 6 to cpu mask aaaa[0m
[2017-04-05 18:36:41][01;30m Binding thread 7 to cpu mask aaaa[0m
[2017-04-05 18:36:41][01;30m Auth id: 586353101953864[0m
[2017-04-05 18:36:41][33m Stratum difficulty set to 10000[0m
[2017-04-05 18:36:43] CPU #2: 66 H, 51.56 H/s[0m
[2017-04-05 18:36:43] CPU #4: 66 H, 51.54 H/s[0m
[2017-04-05 18:36:43] CPU #3: 66 H, 51.14 H/s[0m
[2017-04-05 18:36:43] CPU #1: 66 H, 50.55 H/s[0m
[2017-04-05 18:36:43] CPU #0: 66 H, 50.55 H/s[0m
[2017-04-05 18:36:43] CPU #7: 66 H, 50.03 H/s[0m
[2017-04-05 18:36:43] CPU #6: 66 H, 49.10 H/s[0m
[2017-04-05 18:36:43] CPU #5: 66 H, 47.25 H/s[0m
[2017-04-05 18:36:47] CPU #4: 214 H, 52.14 H/s[0m
[2017-04-05 18:36:47][01;37m [32mAccepted[01;37m 1/1 (100%), 676 H, 402.31 H/s[0m
[2017-04-05 18:37:02] CPU #0: 967 H, 50.67 H/s[0m
[2017-04-05 18:37:02][01;37m [32mAccepted[01;37m 2/2 (100%), 1577 H, 402.43 H/s[0m
[2017-04-05 18:37:42] CPU #1: 3034 H, 51.89 H/s[0m
[2017-04-05 18:37:42] CPU #3: 3070 H, 52.06 H/s[0m
[2017-04-05 18:37:42] CPU #6: 2947 H, 50.00 H/s[0m
[2017-04-05 18:37:43] CPU #2: 3095 H, 52.08 H/s[0m
[2017-04-05 18:37:43] CPU #5: 2837 H, 47.82 H/s[0m
[2017-04-05 18:37:43] CPU #7: 3003 H, 50.53 H/s[0m
[2017-04-05 18:37:47] CPU #4: 3130 H, 52.15 H/s[0m
[2017-04-05 18:38:02] CPU #0: 3029 H, 50.70 H/s[0m
[2017-04-05 18:38:02][01;37m [32mAccepted[01;37m 3/3 (100%), 24.15 kH, 407.23 H/s[0m
[2017-04-05 18:38:42] CPU #1: 3115 H, 52.00 H/s[0m
[2017-04-05 18:38:42] CPU #3: 3125 H, 52.14 H/s[0m
[2017-04-05 18:38:42] CPU #6: 3001 H, 50.08 H/s[0m
[2017-04-05 18:38:42] CPU #2: 3126 H, 52.21 H/s[0m
[2017-04-05 18:38:43] CPU #5: 2871 H, 47.87 H/s[0m
[2017-04-05 18:38:43] CPU #7: 3033 H, 50.55 H/s[0m
[2017-04-05 18:38:47] CPU #4: 3130 H, 52.24 H/s[0m
[2017-04-05 18:38:53] CPU #0: 2586 H, 50.78 H/s[0m
[2017-04-05 18:38:53][01;37m [32mAccepted[01;37m 4/4 (100%), 23.99 kH, 407.88 H/s[0m
[2017-04-05 18:39:06] CPU #6: 1197 H, 50.25 H/s[0m
[2017-04-05 18:39:06][01;37m [32mAccepted[01;37m 5/5 (100%), 22.18 kH, 408.05 H/s[0m
[2017-04-05 18:39:37] CPU #1: 2853 H, 51.82 H/s[0m
[2017-04-05 18:39:37][01;37m [32mAccepted[01;37m 6/6 (100%), 21.92 kH, 407.87 H/s[0m
[2017-04-05 18:39:42] CPU #3: 3130 H, 52.02 H/s[0m
[2017-04-05 18:39:43] CPU #7: 3035 H, 50.64 H/s[0m
[2017-04-05 18:39:43] CPU #5: 2873 H, 47.87 H/s[0m
[2017-04-05 18:39:43] CPU #2: 3134 H, 52.10 H/s[0m
[2017-04-05 18:39:47] CPU #4: 3136 H, 52.14 H/s[0m
[2017-04-05 18:39:48] CPU #0: 2778 H, 50.67 H/s[0m
[2017-04-05 18:39:48][01;37m [32mAccepted[01;37m 7/7 (100%), 22.14 kH, 407.50 H/s[0m
[2017-04-05 18:39:49] CPU #7: 315 H, 50.55 H/s[0m
[2017-04-05 18:39:49][01;37m [32mAccepted[01;37m 8/8 (100%), 19.42 kH, 407.41 H/s[0m
[2017-04-05 18:39:50] CPU #2: 395 H, 52.15 H/s[0m
[2017-04-05 18:39:50][01;37m [32mAccepted[01;37m 9/9 (100%), 16.68 kH, 407.46 H/s[0m
[2017-04-05 18:40:06] CPU #6: 3017 H, 49.96 H/s[0m
[2017-04-05 18:40:07] CPU #4: 1032 H, 52.42 H/s[0m
[2017-04-05 18:40:07][01;37m [32mAccepted[01;37m 10/10 (100%), 16.39 kH, 407.45 H/s[0m
[2017-04-05 18:40:12] CPU #3: 1542 H, 52.38 H/s[0m
[2017-04-05 18:40:12][01;37m [32mAccepted[01;37m 11/11 (100%), 14.81 kH, 407.81 H/s[0m
[2017-04-05 18:40:12] CPU #4: 276 H, 52.51 H/s[0m
[2017-04-05 18:40:12][01;37m [32mAccepted[01;37m 12/12 (100%), 14.05 kH, 407.90 H/s[0m
[2017-04-05 18:40:33] CPU #5: 2397 H, 47.49 H/s[0m
[2017-04-05 18:40:33][01;37m [32mAccepted[01;37m 13/13 (100%), 13.57 kH, 407.52 H/s[0m
[2017-04-05 18:40:36] CPU #1: 3111 H, 52.17 H/s[0m
[2017-04-05 18:40:45] CPU #0: 2906 H, 50.53 H/s[0m
[2017-04-05 18:40:45][01;37m [32mAccepted[01;37m 14/14 (100%), 13.96 kH, 407.73 H/s[0m
[2017-04-05 18:40:49] CPU #7: 3034 H, 50.45 H/s[0m
[2017-04-05 18:40:50] CPU #2: 3130 H, 52.41 H/s[0m
[2017-04-05 18:40:57] CPU #7: 425 H, 50.50 H/s[0m
[2017-04-05 18:40:57][01;37m [32mAccepted[01;37m 15/15 (100%), 16.80 kH, 407.94 H/s[0m
[2017-04-05 18:41:06] CPU #6: 2999 H, 49.98 H/s[0m
[2017-04-05 18:41:12] CPU #3: 3144 H, 52.25 H/s[0m
[2017-04-05 18:41:12] CPU #4: 3152 H, 52.42 H/s[0m
[2017-04-05 18:41:33] CPU #5: 2851 H, 47.76 H/s[0m
[2017-04-05 18:41:37] CPU #1: 3132 H, 51.99 H/s[0m
[2017-04-05 18:41:38] CPU #0: 2660 H, 50.67 H/s[0m
[2017-04-05 18:41:38][01;37m [32mAccepted[01;37m 16/16 (100%), 21.49 kH, 407.98 H/s[0m
April 05, 2017, 10:33:38 AM
I'm beginning to lose patience. I don't want opinions I want data. If I had a Ryzen I'd do it myself.
I need to know how logical cores are mapped to Ryzen HW. If no one with a Ryzen is willing to do the
work then I'll just drop the issue and leave affinity the way it is.
I need to know how logical cores are mapped to Ryzen HW. If no one with a Ryzen is willing to do the
work then I'll just drop the issue and leave affinity the way it is.
April 05, 2017, 10:12:58 AM
0x5555 (0xAAAA is better though because then it leaves logical core 0 unloaded and available leading to better system stability. I haven't seen a performance penalty)
April 05, 2017, 10:05:17 AM
Widows is supposed to manage threads by CCX and then by core.
This is the point I have been trying to make, there are 2 levels of hierarchy, it's not just about the
fragmented L3 cache but also SMT. The miner threads need to be evenly distributed
across the CCXs as well as accross the physical cores within the CCX. Loading 2 threads on one
physical core will reduce performance while another physical core remains idle.
Each physical core should run only one thread when mining cryptonight. It also helps spread the
thermal load.
0x0f0f vs 0x5555, which achieves that?
April 05, 2017, 09:50:50 AM
onedeveloper,
giaggio was running hexxcoin, a lyra2z330 algo. I don't know what the performance is or how it uses the cache for that algo. I was planning on testing lyra2z330 tonight.
Widows is supposed to manage threads by CCX and then by core. It definitely manages them by CCX and I'm not sure about core because I've always set an affinity mask. I've been trying to tell you how it manages affinities by CCX and core but you've been too busy telling me I'm getting it wrong.
ZenFr,
Happy to help! Also, the tool at https://www.paulhempshall.com/io/cpuminer-affinity-setter/ works great and outputs in decimal format.
giaggio was running hexxcoin, a lyra2z330 algo. I don't know what the performance is or how it uses the cache for that algo. I was planning on testing lyra2z330 tonight.
Widows is supposed to manage threads by CCX and then by core. It definitely manages them by CCX and I'm not sure about core because I've always set an affinity mask. I've been trying to tell you how it manages affinities by CCX and core but you've been too busy telling me I'm getting it wrong.
ZenFr,
Happy to help! Also, the tool at https://www.paulhempshall.com/io/cpuminer-affinity-setter/ works great and outputs in decimal format.
April 05, 2017, 08:59:16 AM
Quote
What are the masks to have only one thread per physical core (2 cores/4 threads CPUs (Core i3/i5) nd 4 cores/8 thread CPUs (Core i7)) ?
ZenFr,2C/4T 0xA or 0x5
4C/8T 0xAA or 0x55
April 05, 2017, 08:40:48 AM
You can also use 0x0F0F or other combinations, providing there are only 4 CPUs (bits) active on first two digits and 4 on second.
I hope all is clear now
I hope all is clear now
Almost. Won't a mask of 0xf0f0 result in 4 idle cores and 4 cores with 2 threads each. Don't you want one thread
per physical core?
ZenFr,
2C/4T 0xA or 0x5
4C/8T 0xAA or 0x55
edit: onedeveloper, I was mis-remembering the L3 cache structure on the Ryzen, it's a unified 8mb victim cache per CCX not 2mb L3 victim cache per core. Still, there is a cache bandwidth issue and the nature of the victim cache means that if 8mb per CCX is reached then it starts moving data to the other CCX or if it is full as well it moves to system ram. If you mask 0x5 on Ryzen you mask the process to logical processor 0 and 2, core 1 and 2 of CCX 1. If you mask 0xA on Ryzen you mask the process to logical processor 1 and 3, core 1 and 2 of CCX 1.
I read this reddit thread -> https://www.reddit.com/r/Amd/comments/5ybrxn/ryzen_7_is_actually_behaving_like_a_dual_4c8t/
They linked this image:
Still, they don't explain how windows manages CPU affinities, but the secret is finding the physical CCX for each CPU thread (logical CPU) and adjust the mask accordingly. User "giaggio" used that mask I said above and had a good result: 640 hashes at only 35 Watts (due to the iddle threads/cores on each CCX).
April 05, 2017, 08:34:15 AM
You can also use 0x0F0F or other combinations, providing there are only 4 CPUs (bits) active on first two digits and 4 on second.
I hope all is clear now
I hope all is clear now
Almost. Won't a mask of 0xf0f0 result in 4 idle cores and 4 cores with 2 threads each. Don't you want one thread
per physical core?
Yes. 4 Idle cores per CCX. You don't earn better hash power on Cryptonight once you cover your L3 cache and each CCX has only 8MB cache, so 4 threads per CCX plus 4 threads free for playing DOTA2 and do some browsing at the same time
Jump to: