Hi Joblo! 3.7.8 avx-sha is better than ever! Im mining m7m algo, but I mine with both GPUs and Ryzen. The 16thread mining are slowing down the GPUs mining. How could I set CPU affinity for all threads but CPU0 (or threads 0 and 1)? I searched for an option to do it, but I havent found nothing  EDIT:' I found it: https://phempshall.github.io/cpuminer-affinity-setter/works  |
|
|
|
Making 2 packages is more work for me, I'm trying to reduce the work.
I'm leaning toward replacing avx2-sha with avx-sha unless someone shows a good
reason for avx2-sha.
Edit: a couple more points
AVX2 and SHA improve different algos and different parts of the same algos. AVX won't have
any effect on SHA code on Ryzen CPUs. There are no technical concerns with AVX-SHA.
The only question is performance on algos that have use AVX2. The best algo to test this is
lyra2v2, it is almost 100% AVX2 and not too hard on memory so it will expose any weaknesses
in AVX2 on Ryzen.
I'm getting around 1.6~2MH/s in Lyra2z. But I'm getting low difficult share errors on every share: [2017-12-19 17:45:42] Starting Stratum on stratum+tcp://us-east.lyra2z-hub.miningpoolhub.com:20581
[2017-12-19 17:45:42] 16 miner threads started, using 'lyra2rev2' algorithm.
[2017-12-19 17:45:43] Stratum difficulty set to 10
[2017-12-19 17:46:05] CPU #9: 2097.15 kH, 116.83 kH/s
[2017-12-19 17:46:05] CPU #11: 2097.15 kH, 116.65 kH/s
[2017-12-19 17:46:05] CPU #7: 2097.15 kH, 116.33 kH/s
[2017-12-19 17:46:06] CPU #15: 2097.15 kH, 114.68 kH/s
[2017-12-19 17:46:06] CPU #6: 2097.15 kH, 111.85 kH/s
[2017-12-19 17:46:06] CPU #3: 2097.15 kH, 111.58 kH/s
[2017-12-19 17:46:06] CPU #14: 2097.15 kH, 110.05 kH/s
[2017-12-19 17:46:07] CPU #10: 2097.15 kH, 108.93 kH/s
[2017-12-19 17:46:07] CPU #5: 2097.15 kH, 107.02 kH/s
[2017-12-19 17:46:07] CPU #8: 2097.15 kH, 106.52 kH/s
[2017-12-19 17:46:07] CPU #2: 2097.15 kH, 106.20 kH/s
[2017-12-19 17:46:09] CPU #1: 2097.15 kH, 98.64 kH/s
[2017-12-19 17:46:10] CPU #13: 2097.15 kH, 93.44 kH/s
[2017-12-19 17:46:16] CPU #4: 2097.15 kH, 73.31 kH/s
[2017-12-19 17:46:16] CPU #0: 2097.15 kH, 73.11 kH/s
[2017-12-19 17:46:20] CPU #12: 2097.15 kH, 64.31 kH/s
[2017-12-19 17:46:39] Stratum difficulty set to 7
[2017-12-19 17:46:42] CPU #13: 3174.84 kH, 98.57 kH/s
[2017-12-19 17:46:42] Rejected 1/1 (100.0%), 34.63 MH, 1634.59 kH/s
[2017-12-19 17:46:42] reject reason: low difficulty share of 8.935987400308036e-8
[2017-12-19 17:46:42] factor reduced to : 0.67 Is it miner-related or pool-related? User error, look carefullly at the algo. Another note about lyra2z, 4way is likely slower due to previously mentioned issues with it. Damn! You are right Too many "Lyras" |
|
|
|
Making 2 packages is more work for me, I'm trying to reduce the work.
I'm leaning toward replacing avx2-sha with avx-sha unless someone shows a good
reason for avx2-sha.
Edit: a couple more points
AVX2 and SHA improve different algos and different parts of the same algos. AVX won't have
any effect on SHA code on Ryzen CPUs. There are no technical concerns with AVX-SHA.
The only question is performance on algos that have use AVX2. The best algo to test this is
lyra2v2, it is almost 100% AVX2 and not too hard on memory so it will expose any weaknesses
in AVX2 on Ryzen.
I'm getting around 1.6~2MH/s in Lyra2z. But I'm getting low difficult share errors on every share: [2017-12-19 17:45:42] Starting Stratum on stratum+tcp://us-east.lyra2z-hub.miningpoolhub.com:20581
[2017-12-19 17:45:42] 16 miner threads started, using 'lyra2rev2' algorithm.
[2017-12-19 17:45:43] Stratum difficulty set to 10
[2017-12-19 17:46:05] CPU #9: 2097.15 kH, 116.83 kH/s
[2017-12-19 17:46:05] CPU #11: 2097.15 kH, 116.65 kH/s
[2017-12-19 17:46:05] CPU #7: 2097.15 kH, 116.33 kH/s
[2017-12-19 17:46:06] CPU #15: 2097.15 kH, 114.68 kH/s
[2017-12-19 17:46:06] CPU #6: 2097.15 kH, 111.85 kH/s
[2017-12-19 17:46:06] CPU #3: 2097.15 kH, 111.58 kH/s
[2017-12-19 17:46:06] CPU #14: 2097.15 kH, 110.05 kH/s
[2017-12-19 17:46:07] CPU #10: 2097.15 kH, 108.93 kH/s
[2017-12-19 17:46:07] CPU #5: 2097.15 kH, 107.02 kH/s
[2017-12-19 17:46:07] CPU #8: 2097.15 kH, 106.52 kH/s
[2017-12-19 17:46:07] CPU #2: 2097.15 kH, 106.20 kH/s
[2017-12-19 17:46:09] CPU #1: 2097.15 kH, 98.64 kH/s
[2017-12-19 17:46:10] CPU #13: 2097.15 kH, 93.44 kH/s
[2017-12-19 17:46:16] CPU #4: 2097.15 kH, 73.31 kH/s
[2017-12-19 17:46:16] CPU #0: 2097.15 kH, 73.11 kH/s
[2017-12-19 17:46:20] CPU #12: 2097.15 kH, 64.31 kH/s
[2017-12-19 17:46:39] Stratum difficulty set to 7
[2017-12-19 17:46:42] CPU #13: 3174.84 kH, 98.57 kH/s
[2017-12-19 17:46:42] Rejected 1/1 (100.0%), 34.63 MH, 1634.59 kH/s
[2017-12-19 17:46:42] reject reason: low difficulty share of 8.935987400308036e-8
[2017-12-19 17:46:42] factor reduced to : 0.67 Is it miner-related or pool-related? |
|
|
|
I've uploaded a new windows binaries package of v3.7.7 to git with support for SHA. I also trimmed some of the file names to remove redundancy. 4way includes avx2 avx2 includes avx avx includes aes and sse4.2 It's avaiable on the releases page or this direct link: https://github.com/JayDDee/cpuminer-opt/files/1569739/cpuminer-opt-3.7.7-windows-v2.zipBe careful with sha, only the AMD Ryzen family supports it at this time. Consider this a beta for the new Windows build system. Great! SHA works great! Your miner is blazing fast! I will do the benchmarks like I did with 4ward build. Apologize me, but can I ask one more build? SHA AVX (not AVX2) version. I explain: Ryzen doesn't have a "fine" AVX2 implementation. In some algos, AVX is faster than AVX2. We are trying to find the best setup with SHA, so maybe AVX setup can give one more option to try. What do you think? That's a very reasonable request and doable. However I'm trying to reduce the number of binaries I build, 8 is too many. Also I'm hesitant to "downgrade" the technology, it just doesn't feel right. Let me think about it and I'll do something for next release. I'm considering eliminating the sse42 build. There are no specific optimizations targetting sse42 so there should no performance loss when using the sse2 build. If there are no reports showing a benefit to the sse42 build it will be removed. There is two possibilities: if - Make a 3.7.7 build with only AVX and SHA to see if SHA-like algos takes advantage of AVX instead AVX2; If yes - Split into two packages: normal and SHA zips (or Ryzen zips). SHA doubles the build count, so split into different package could reduce the "useless" executables (to non-Ryzen users). If no - Remove AVX-SHA from future builds. |
|
|
|
|
Segundo o viajante do futuro, o BTC vai mudar a sociedade completamente, e em 2025 os ricos terão suas fortunas em btc.
Quanto ao vídeo, só posso dizer: I L U M I N I G H T
|
|
|
|
I've uploaded a new windows binaries package of v3.7.7 to git with support for SHA. I also trimmed some of the file names to remove redundancy. 4way includes avx2 avx2 includes avx avx includes aes and sse4.2 It's avaiable on the releases page or this direct link: https://github.com/JayDDee/cpuminer-opt/files/1569739/cpuminer-opt-3.7.7-windows-v2.zipBe careful with sha, only the AMD Ryzen family supports it at this time. Consider this a beta for the new Windows build system. Great! SHA works great! Your miner is blazing fast! I will do the benchmarks like I did with 4ward build. Apologize me, but can I ask one more build? SHA AVX (not AVX2) version. I explain: Ryzen doesn't have a "fine" AVX2 implementation. In some algos, AVX is faster than AVX2. We are trying to find the best setup with SHA, so maybe AVX setup can give one more option to try. What do you think? |
|
|
|
Thanks for that. Do you have a howto guide? I need to file it for when I finally upgrade my build environment With your permission I will add your link to the OP. I'm cross compiling cpuminer-opt for my own usage for some time (since I posted the instructions here) You can link to my github https://github.com/yuzi-co/miners/releases/download/1/cpuminer-opt-3.7.7-4ward.7zIt includes all the windows versions you release (compiled with openssl 1.1) + sha + all necessary dlls One thing I couldn't resolve is that neoscrypt always fails to run (same in My9bot's version) Thank you! I did some benchmarks (Ryzen 7 1700 at 3.7GHz) with your package SHA256T - SHA 16 THREADS [2017-12-18 14:20:40] 16 miner threads started, using 'sha256t' algorithm.
[2017-12-18 14:20:40] Total: 1572.86 kH, 22.62 MH/s
[2017-12-18 14:20:45] Total: 278.74 MH, 58.72 MH/s
[2017-12-18 14:20:50] Total: 243.37 MH, 58.17 MH/s
[2017-12-18 14:20:55] Total: 276.47 MH, 58.41 MH/s
[2017-12-18 14:21:00] Total: 284.05 MH, 58.46 MH/s
[2017-12-18 14:21:05] Total: 279.11 MH, 59.02 MH/s
[2017-12-18 14:21:10] Total: 266.39 MH, 59.40 MH/s
[2017-12-18 14:21:15] Total: 292.94 MH, 59.38 MH/s SHA256T - SHA 8 THREADS [2017-12-18 14:23:25] 8 miner threads started, using 'sha256t' algorithm.
[2017-12-18 14:23:25] Total: 1048.58 kH, 20.97 MH/s
[2017-12-18 14:23:30] Total: 176.50 MH, 41.74 MH/s
[2017-12-18 14:23:35] Total: 188.22 MH, 41.66 MH/s
[2017-12-18 14:23:40] Total: 187.26 MH, 41.78 MH/s
[2017-12-18 14:23:45] Total: 203.56 MH, 41.76 MH/s
[2017-12-18 14:23:50] Total: 208.79 MH, 41.86 MH/s SKEIN - SHA 16 THREADS ********** cpuminer-opt 3.7.7 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX2 and SHA extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
CPU: AMD Ryzen 7 1700 Eight-Core Processor .
SW built on Dec 17 2017 with GCC 6.2.1.
CPU features: SSE2 AES AVX AVX2 SHA.
SW features: SSE2 AES AVX AVX2 SHA.
Algo features: SSE2 SHA.
Start mining with SSE2 SHA.
[2017-12-18 14:24:40] 16 miner threads started, using 'skein' algorithm.
[2017-12-18 14:24:41] Total: 524.29 kH, 1483.29 kH/s
[2017-12-18 14:24:45] Total: 61.07 MH, 23.24 MH/s
[2017-12-18 14:24:50] Total: 111.79 MH, 23.29 MH/s
[2017-12-18 14:24:55] Total: 116.39 MH, 23.27 MH/s
[2017-12-18 14:25:00] Total: 115.93 MH, 23.33 MH/s
[2017-12-18 14:25:05] Total: 115.96 MH, 23.22 MH/s SKEIN - SHA 8 THREADS ********** cpuminer-opt 3.7.7 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX2 and SHA extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
CPU: AMD Ryzen 7 1700 Eight-Core Processor .
SW built on Dec 17 2017 with GCC 6.2.1.
CPU features: SSE2 AES AVX AVX2 SHA.
SW features: SSE2 AES AVX AVX2 SHA.
Algo features: SSE2 SHA.
Start mining with SSE2 SHA.
[2017-12-18 14:25:38] 8 miner threads started, using 'skein' algorithm.
[2017-12-18 14:25:38] Total: 1572.86 kH, 6930.61 kH/s
[2017-12-18 14:25:43] Total: 79.42 MH, 18.37 MH/s
[2017-12-18 14:25:48] Total: 82.68 MH, 18.31 MH/s
[2017-12-18 14:25:53] Total: 89.29 MH, 18.31 MH/s
[2017-12-18 14:25:58] Total: 82.48 MH, 18.30 MH/s M7M - SHA 16 THREADS ********** cpuminer-opt 3.7.7 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX2 and SHA extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
CPU: AMD Ryzen 7 1700 Eight-Core Processor .
SW built on Dec 17 2017 with GCC 6.2.1.
CPU features: SSE2 AES AVX AVX2 SHA.
SW features: SSE2 AES AVX AVX2 SHA.
Algo features: SSE2 AES AVX AVX2 SHA.
Start mining with AES AVX2 SHA.
[2017-12-18 14:26:51] 16 miner threads started, using 'm7m' algorithm.
[2017-12-18 14:26:58] Total: 1048.58 kH, 153.21 kH/s
[2017-12-18 14:27:03] Total: 1475.41 kH, 298.13 kH/s
[2017-12-18 14:27:08] Total: 1462.74 kH, 299.35 kH/s
[2017-12-18 14:27:13] Total: 1473.17 kH, 293.62 kH/s
[2017-12-18 14:27:19] Total: 1470.94 kH, 292.78 kH/s
[2017-12-18 14:27:22] Total: 1446.18 kH, 287.93 kH/s
[2017-12-18 14:27:23] Total: 1314.45 kH, 293.83 kH/s M7M - SHA 8 THREADS ********** cpuminer-opt 3.7.7 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX2 and SHA extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
CPU: AMD Ryzen 7 1700 Eight-Core Processor .
SW built on Dec 17 2017 with GCC 6.2.1.
CPU features: SSE2 AES AVX AVX2 SHA.
SW features: SSE2 AES AVX AVX2 SHA.
Algo features: SSE2 AES AVX AVX2 SHA.
Start mining with AES AVX2 SHA.
[2017-12-18 14:27:44] 8 miner threads started, using 'm7m' algorithm.
[2017-12-18 14:27:48] Total: 393.22 kH, 87.37 kH/s
[2017-12-18 14:27:49] Total: 742.73 kH, 226.83 kH/s
[2017-12-18 14:27:54] Total: 453.60 kH, 229.37 kH/s
[2017-12-18 14:27:59] Total: 1144.11 kH, 228.59 kH/s
[2017-12-18 14:28:04] Total: 1099.87 kH, 224.53 kH/s
[2017-12-18 14:28:09] Total: 1091.55 kH, 222.76 kH/s LBRY - SHA 16 THREADS ********** cpuminer-opt 3.7.7 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX2 and SHA extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
CPU: AMD Ryzen 7 1700 Eight-Core Processor .
SW built on Dec 17 2017 with GCC 6.2.1.
CPU features: SSE2 AES AVX AVX2 SHA.
SW features: SSE2 AES AVX AVX2 SHA.
Algo features: SSE2 AVX AVX2 SHA.
Start mining with AVX2 SHA.
[2017-12-18 14:29:03] 16 miner threads started, using 'lbry' algorithm.
[2017-12-18 14:29:03] Total: 393.22 kH, 1994.04 kH/s
[2017-12-18 14:29:08] Total: 28.31 MH, 10.36 MH/s
[2017-12-18 14:29:13] Total: 46.71 MH, 10.34 MH/s
[2017-12-18 14:29:18] Total: 49.09 MH, 10.32 MH/s
[2017-12-18 14:29:23] Total: 51.59 MH, 10.33 MH/s
[2017-12-18 14:29:28] Total: 51.65 MH, 10.29 MH/s
[2017-12-18 14:29:33] Total: 50.62 MH, 10.32 MH/s LBRY - SHA 8 THREADS ********** cpuminer-opt 3.7.7 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX2 and SHA extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
CPU: AMD Ryzen 7 1700 Eight-Core Processor .
SW built on Dec 17 2017 with GCC 6.2.1.
CPU features: SSE2 AES AVX AVX2 SHA.
SW features: SSE2 AES AVX AVX2 SHA.
Algo features: SSE2 AVX AVX2 SHA.
Start mining with AVX2 SHA.
[2017-12-18 14:29:54] 8 miner threads started, using 'lbry' algorithm.
[2017-12-18 14:29:54] Total: 655.36 kH, 4567.30 kH/s
[2017-12-18 14:29:59] Total: 18.29 MH, 7300.38 kH/s
[2017-12-18 14:30:04] Total: 36.52 MH, 7297.99 kH/s
[2017-12-18 14:30:09] Total: 36.49 MH, 7293.69 kH/s
[2017-12-18 14:30:14] Total: 36.46 MH, 7234.66 kH/s
[2017-12-18 14:30:19] Total: 36.17 MH, 7211.15 kH/s MYR-GR - SHA 16 THREADS ********** cpuminer-opt 3.7.7 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX2 and SHA extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
CPU: AMD Ryzen 7 1700 Eight-Core Processor .
SW built on Dec 17 2017 with GCC 6.2.1.
CPU features: SSE2 AES AVX AVX2 SHA.
SW features: SSE2 AES AVX AVX2 SHA.
Algo features: SSE2 AES AVX AVX2 SHA.
Start mining with AES AVX2 SHA.
[2017-12-18 14:31:08] 16 miner threads started, using 'myr-gr' algorithm.
[2017-12-18 14:31:08] Total: 3145.73 kH, 8517.45 kH/s
[2017-12-18 14:31:13] Total: 22.12 MH, 11.17 MH/s
[2017-12-18 14:31:18] Total: 47.95 MH, 11.11 MH/s
[2017-12-18 14:31:23] Total: 44.93 MH, 11.17 MH/s
[2017-12-18 14:31:26] Total: 44.12 MH, 11.06 MH/s MYR-GR - SHA 8 THREADS ********** cpuminer-opt 3.7.7 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX2 and SHA extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
CPU: AMD Ryzen 7 1700 Eight-Core Processor .
SW built on Dec 17 2017 with GCC 6.2.1.
CPU features: SSE2 AES AVX AVX2 SHA.
SW features: SSE2 AES AVX AVX2 SHA.
Algo features: SSE2 AES AVX AVX2 SHA.
Start mining with AES AVX2 SHA.
[2017-12-18 14:32:04] 8 miner threads started, using 'myr-gr' algorithm.
[2017-12-18 14:32:04] Total: 1107.11 kH, 5887.11 kH/s
[2017-12-18 14:32:09] Total: 31.06 MH, 9538.90 kH/s
[2017-12-18 14:32:14] Total: 34.63 MH, 9553.20 kH/s
[2017-12-18 14:32:19] Total: 37.34 MH, 9566.10 kH/s
[2017-12-18 14:32:24] Total: 31.56 MH, 9568.59 kH/s Is there a possibility to make a SHA version with AES-AVX/AES-AVX2/4WAY to improve the tests? |
|
|
|
Ya, the default affinity was choosing virtual threads instead physical ones. Damn! 6MH/s!
All Ryzen users should take note. Intel chooses one thread per core before using HT. In fact. Joblo, is there an updated algo list that receive boost from SHA hardware acceleration? I found a little list some pages before: sha256t, lbry, skein, myr-groestl, m7m. Are there more algos? I converted all of them at the time and I don't recall any new algos that can use it. What about nist5? Can you try that again? I'd like to understand what's going on there. I get good performance on my Intel. I reduced overclock (to keep everything cold). New results with NIST5: NIST5 4way 8 threads with --cpu-affinity 0x5555 [2017-12-17 20:33:17] nist5 block 14635, diff 14699.054
[2017-12-17 20:33:27] CPU #6: 2097.15 kH, 209.42 kH/s
[2017-12-17 20:33:27] CPU #2: 2097.15 kH, 207.48 kH/s
[2017-12-17 20:33:27] CPU #5: 2097.15 kH, 205.79 kH/s
[2017-12-17 20:33:27] CPU #7: 2097.15 kH, 205.61 kH/s
[2017-12-17 20:33:27] CPU #4: 2097.15 kH, 204.96 kH/s
[2017-12-17 20:33:27] CPU #1: 2097.15 kH, 204.46 kH/s
[2017-12-17 20:33:27] CPU #0: 2097.15 kH, 204.01 kH/s
[2017-12-17 20:33:27] CPU #3: 2097.15 kH, 199.72 kH/s NIST5 16 threads [2017-12-17 20:47:55] nist5 block 14649, diff 22837.326
[2017-12-17 20:47:55] CPU #2: 667.71 kH, 121.83 kH/s
[2017-12-17 20:47:55] CPU #3: 672.92 kH, 122.76 kH/s
[2017-12-17 20:47:55] CPU #0: 454.52 kH, 83.08 kH/s
[2017-12-17 20:47:55] CPU #1: 653.82 kH, 119.54 kH/s
[2017-12-17 20:47:55] CPU #14: 647.14 kH, 118.14 kH/s
[2017-12-17 20:47:55] CPU #7: 657.04 kH, 119.95 kH/s
[2017-12-17 20:47:55] CPU #6: 635.59 kH, 116.06 kH/s
[2017-12-17 20:47:55] CPU #11: 681.85 kH, 124.55 kH/s
[2017-12-17 20:47:55] CPU #5: 682.78 kH, 124.85 kH/s
[2017-12-17 20:47:55] CPU #4: 570.23 kH, 104.24 kH/s
[2017-12-17 20:47:55] CPU #12: 565.09 kH, 103.26 kH/s
[2017-12-17 20:47:55] CPU #10: 681.59 kH, 124.53 kH/s
[2017-12-17 20:47:55] CPU #8: 617.07 kH, 112.53 kH/s
[2017-12-17 20:47:55] CPU #9: 684.27 kH, 124.89 kH/s
[2017-12-17 20:47:55] CPU #15: 669.73 kH, 122.23 kH/s
[2017-12-17 20:47:55] CPU #13: 642.05 kH, 117.12 kH/s NIST5 AES-AVX2 8 threads with --cpu-affinity 0x5555 [2017-12-17 20:59:30] nist5 block 14655, diff 22762.164
[2017-12-17 20:59:36] CPU #4: 2097.15 kH, 369.94 kH/s
[2017-12-17 20:59:36] CPU #5: 2097.15 kH, 365.38 kH/s
[2017-12-17 20:59:36] CPU #7: 2097.15 kH, 365.42 kH/s
[2017-12-17 20:59:36] CPU #6: 2097.15 kH, 365.26 kH/s
[2017-12-17 20:59:36] CPU #3: 2097.15 kH, 365.13 kH/s
[2017-12-17 20:59:36] CPU #0: 2097.15 kH, 359.60 kH/s
[2017-12-17 20:59:36] CPU #1: 2097.15 kH, 359.14 kH/s
[2017-12-17 20:59:36] CPU #2: 2097.15 kH, 356.60 kH/s EDIT1: NIST5 AES-AVX 8 threads with --cpu-affinity 0x5555 [2017-12-17 21:02:19] nist5 block 14657, diff 22797.808
[2017-12-17 21:02:26] CPU #6: 2097.15 kH, 374.14 kH/s
[2017-12-17 21:02:26] CPU #5: 2097.15 kH, 373.53 kH/s
[2017-12-17 21:02:26] CPU #2: 2097.15 kH, 370.56 kH/s
[2017-12-17 21:02:26] CPU #7: 2097.15 kH, 369.28 kH/s
[2017-12-17 21:02:26] CPU #4: 2097.15 kH, 367.82 kH/s
[2017-12-17 21:02:26] CPU #0: 2097.15 kH, 367.53 kH/s
[2017-12-17 21:02:26] CPU #1: 2097.15 kH, 365.98 kH/s
[2017-12-17 21:02:26] CPU #3: 2097.15 kH, 365.38 kH/s EDIT2: what do you need? Wich algos are affected by SHA acceleration? |
|
|
|
Ya, the default affinity was choosing virtual threads instead physical ones. Damn! 6MH/s!
All Ryzen users should take note. Intel chooses one thread per core before using HT. In fact. Joblo, is there an updated algo list that receive boost from SHA hardware acceleration? I found a little list some pages before: sha256t, lbry, skein, myr-groestl, m7m. Are there more algos? |
|
|
|
Tribus 4way 8 threads: [2017-12-17 15:45:48][2017-12-17 15:49:10] [2017-12-17 17:05:32] tribus block 449483, diff 735.578
[2017-12-17 17:05:32] CPU #7: 461.65 kH, 398.07 kH/s
[2017-12-17 17:05:32] CPU #6: 460.63 kH, 398.21 kH/s
[2017-12-17 17:05:32] CPU #5: 460.43 kH, 397.70 kH/s
[2017-12-17 17:05:32] CPU #2: 460.88 kH, 397.74 kH/s
[2017-12-17 17:05:32] CPU #4: 460.51 kH, 397.76 kH/s
[2017-12-17 17:05:32] CPU #3: 460.82 kH, 398.03 kH/s
[2017-12-17 17:05:32] CPU #0: 454.80 kH, 393.86 kH/s
[2017-12-17 17:05:32] CPU #1: 463.35 kH, 399.53 kH/s Apparently Tribus 4way likes SMT/HT here. It's interesting that the thread rate didn't increase with fewer threads. Were the threads spread over all 8 cores? You can try "-t 8 --cpu-affinity 0x5555" to select alternate vcores. [2017-12-17 17:34:59] [2017-12-17 17:36:25] tribus block 449526, diff 130.915
[2017-12-17 17:36:25] CPU #6: 5670.24 kH, 753.19 kH/s
[2017-12-17 17:36:25] CPU #5: 5840.23 kH, 775.66 kH/s
[2017-12-17 17:36:25] CPU #0: 69.55 kH, 763.09 kH/s
[2017-12-17 17:36:25] CPU #7: 5672.16 kH, 753.14 kH/s
[2017-12-17 17:36:25] CPU #4: 5766.59 kH, 765.78 kH/s
[2017-12-17 17:36:25] CPU #2: 5597.96 kH, 743.19 kH/s
[2017-12-17 17:36:25] CPU #3: 5665.52 kH, 752.36 kH/s
[2017-12-17 17:36:25] CPU #1: 5690.77 kH, 755.51 kH/s
[2017-12-17 17:36:26] Accepted 2/2 (100%), 39.97 MH, 6061.92 kH/s Ya, the default affinity was choosing virtual threads instead physical ones. Damn! 6MH/s! |
|
|
|
I have a Ryzen 7 1700 at 3.7GHz. The 4way is around 15% slower than AES-AVX/AVX2 mining nist5. Around 240KH/s per core (8 threads) to 4way and 270KH/s per core to AES-AVX2. Its working stable, but with less performance. I can get 2.1~2.2MH/s NIST5.
This is very interesting feedback. I get 340 kH/s per thread 4way vs 255 kH/s AVX2 1way on my i7-6700K @4GHz. Something isn't right, need lots of details to eliminate simple stuff. Can you post the startup for both? None of the following should cause that much of a difference, but it helps to quantify. AMD AVX2 performance is known to be slower than AVX. Try running a test with just AVX2 and again with AVX to compare. 4way uses 4 time the memory of plain AVX2. This will expose any cache performance issues. Try running fewer threads to see if performance (total, not just per thread) improves. Try tribus algo, it's pure 4way parallel while nist5 has a serial component which reduces gain and adds some overhead. Thanks for the reply. About Tribus (3.7.7 version): Tribus AVX 16 threads: [2017-12-17 15:45:48] tribus block 449382, diff 297.717
[2017-12-17 15:45:48] CPU #3: 73.32 kH, 226.66 kH/s
[2017-12-17 15:45:48] CPU #2: 60.95 kH, 225.42 kH/s
[2017-12-17 15:45:48] CPU #1: 68.89 kH, 228.54 kH/s
[2017-12-17 15:45:48] CPU #0: 59.57 kH, 220.31 kH/s
[2017-12-17 15:45:48] CPU #7: 71.66 kH, 226.42 kH/s
[2017-12-17 15:45:48] CPU #4: 47.67 kH, 206.94 kH/s
[2017-12-17 15:45:48] CPU #14: 69.70 kH, 228.19 kH/s
[2017-12-17 15:45:48] CPU #6: 66.07 kH, 226.71 kH/s
[2017-12-17 15:45:48] CPU #12: 36.67 kH, 223.24 kH/s
[2017-12-17 15:45:48] CPU #15: 69.95 kH, 228.24 kH/s
[2017-12-17 15:45:48] CPU #11: 66.53 kH, 225.95 kH/s
[2017-12-17 15:45:48] CPU #5: 70.96 kH, 227.81 kH/s
[2017-12-17 15:45:48] CPU #10: 312.06 kH, 275.75 kH/s
[2017-12-17 15:45:48] CPU #8: 43.73 kH, 172.57 kH/s
[2017-12-17 15:45:48] CPU #9: 68.83 kH, 238.64 kH/s
[2017-12-17 15:45:48] CPU #13: 72.51 kH, 228.39 kH/s Tribus AVX2 16 threads: [2017-12-17 15:45:48][2017-12-17 15:49:10] tribus block 449390, diff 254.451
[2017-12-17 15:49:10] CPU #4: 97.38 kH, 211.38 kH/s
[2017-12-17 15:49:10] CPU #6: 110.08 kH, 237.92 kH/s
[2017-12-17 15:49:10] CPU #7: 110.38 kH, 238.04 kH/s
[2017-12-17 15:49:10] CPU #0: 103.07 kH, 221.32 kH/s
[2017-12-17 15:49:10] CPU #1: 109.05 kH, 234.17 kH/s
[2017-12-17 15:49:10] CPU #9: 109.41 kH, 238.00 kH/s
[2017-12-17 15:49:10] CPU #8: 108.26 kH, 234.98 kH/s
[2017-12-17 15:49:10] CPU #13: 109.99 kH, 238.22 kH/s
[2017-12-17 15:49:10] CPU #5: 112.40 kH, 241.36 kH/s
[2017-12-17 15:49:10] CPU #11: 111.49 kH, 239.40 kH/s
[2017-12-17 15:49:10] CPU #3: 111.29 kH, 238.97 kH/s
[2017-12-17 15:49:10] CPU #15: 110.46 kH, 238.21 kH/s
[2017-12-17 15:49:10] CPU #2: 110.69 kH, 237.67 kH/s
[2017-12-17 15:49:10] CPU #10: 111.39 kH, 239.19 kH/s
[2017-12-17 15:49:10] CPU #14: 110.70 kH, 237.20 kH/s
[2017-12-17 15:49:10] CPU #12: 94.46 kH, 199.39 kH/s
[2017-12-17 15:49:15] CPU #12: 836.08 kH, 196.43 kH/s
[2017-12-17 15:49:15] Accepted 1/1 (100%), 2472.11 kH, 3722.47 kH/s Tribus 4way 16 threads: [2017-12-17 15:45:48][2017-12-17 15:49:10] [2017-12-17 15:50:38] tribus block 449392, diff 221.049
[2017-12-17 15:50:38] CPU #0: 2552.29 kH, 340.11 kH/s
[2017-12-17 15:50:38] CPU #1: 3076.95 kH, 410.02 kH/s
[2017-12-17 15:50:38] CPU #12: 2199.45 kH, 293.25 kH/s
[2017-12-17 15:50:38] CPU #8: 2508.86 kH, 334.41 kH/s
[2017-12-17 15:50:38] CPU #14: 2807.39 kH, 374.11 kH/s
[2017-12-17 15:50:38] CPU #9: 3002.02 kH, 400.25 kH/s
[2017-12-17 15:50:38] CPU #2: 2978.50 kH, 396.85 kH/s
[2017-12-17 15:50:38] CPU #3: 2993.07 kH, 398.79 kH/s
[2017-12-17 15:50:38] CPU #5: 2997.27 kH, 399.67 kH/s
[2017-12-17 15:50:38] CPU #4: 2927.24 kH, 390.44 kH/s
[2017-12-17 15:50:38] CPU #6: 2954.16 kH, 393.72 kH/s
[2017-12-17 15:50:38] CPU #7: 2983.57 kH, 397.69 kH/s
[2017-12-17 15:50:38] CPU #11: 3005.27 kH, 400.79 kH/s
[2017-12-17 15:50:38] CPU #15: 2946.88 kH, 393.06 kH/s
[2017-12-17 15:50:38] CPU #10: 2947.45 kH, 392.77 kH/s
[2017-12-17 15:50:38] CPU #13: 2742.90 kH, 365.66 kH/s Tribus 4way 8 threads: [2017-12-17 15:45:48][2017-12-17 15:49:10] [2017-12-17 17:05:32] tribus block 449483, diff 735.578
[2017-12-17 17:05:32] CPU #7: 461.65 kH, 398.07 kH/s
[2017-12-17 17:05:32] CPU #6: 460.63 kH, 398.21 kH/s
[2017-12-17 17:05:32] CPU #5: 460.43 kH, 397.70 kH/s
[2017-12-17 17:05:32] CPU #2: 460.88 kH, 397.74 kH/s
[2017-12-17 17:05:32] CPU #4: 460.51 kH, 397.76 kH/s
[2017-12-17 17:05:32] CPU #3: 460.82 kH, 398.03 kH/s
[2017-12-17 17:05:32] CPU #0: 454.80 kH, 393.86 kH/s
[2017-12-17 17:05:32] CPU #1: 463.35 kH, 399.53 kH/s Apparently Tribus 4way likes SMT/HT here. |
|
|
|
Thank you! EDIT: Starting miner it asks for libcrypto-1_1-x64.dll. Do I need it or just have to rename the libcrypto1.0.0.dll? EDIT2: Solved by installing OpenSSL 1.1 x64. |
|
|
|
cpuminer-opt-3.7.6 is released. Added lyra2h algo for Hppcoin. Added support for more than 64 CPUs. Optimized shavite with AES, improves x11 etc. Get it on git: https://github.com/JayDDee/cpuminer-opt/releasesMore detailed release notes: Lyra2h has not been tested. It is virtually a clone of lyra2z so it should work. Please report any problems. Support for over 64 CPU is limited in that specifying --cpu-affinity has no effect. The arg will be ignored and he default affinity will be used. This has not been tested either so if anyone has the ability to test it please do so and report. There are no new 4way algos this release but optiizing shavite came as a surprise and helps all CPUs with AES. The past two releases have also seen some reworking of some existing SIMD code as I learn new techniques. It should be more efficient but not likely to produce a significant speed up. There are currently 2 4way blockers. BMW is blocking full optimization of x11 and blake256 is blocking m7m. I'd like to get those resolved but I'm stuck at the moment. Since m7m is CPU only I'd like to prioritize that algo. A few algos have 4way enabled bur are either untested or have known problems that affect performance. Tested working: skein, keccak, keccakc, nist5, tribus. Enabled untested: skein2, jha, whirlpool, pentablake. Enabled with known problems: blake256 lane corruption: lyra2z, decred, blake. These algos operate in 2way mode due to invalid hash in 2 lanes. Kudos for you! Awesome miner  Lets to the feedback: I have a Ryzen 7 1700 at 3.7GHz. The 4way is around 15% slower than AES-AVX/AVX2 mining nist5. Around 240KH/s per core (8 threads) to 4way and 270KH/s per core to AES-AVX2. Its working stable, but with less performance. I can get 2.1~2.2MH/s NIST5. I would like to see SHA enabled and working in Windows, but I saw how difficult are. But, if I could help, I can allow you to connect to my machine to try something. I dont have knowledge about coding, but want help to compile a SHA miner. |
|
|
|
Just copy 1650 strap to higher frequencies?
I'm using a strap based on 1650 strap plus 0 Tfaw, 0 Tfaw32 and 18 ACTRD. But I have a 460 with 560 bios. I can only hit 436H/s at 38W (GPU-Z measure) 1150/2030. What detailed settings are you using?
No, just to last one...and theres no 1650 strap on RX560 micron My bad  1625, in the case |
|
|
|
Very nice hashrate but some seems electric value high and can graphic card more tired seems
I hope you like this new improved version  Where is your ultra-mega-turbo-blaster-lastest improved version? On my PC? But I already stated elsewhere that its only for this card https://www.gigabyte.com/Graphics-Card/GV-RX560GAMING-OC-4GD-rev-10#kfand slightly modified (nothing special, just put high quality thermal paste on GPU and memory instead garbage Gigabyte put there) All other micron based RX560s can expect 14.5-15.5MH/s depending if they have additional power connector, and how good is their cooling) I'll try to get 16.5+ stable soon, just for fun Just copy 1650 strap to higher frequencies? I'm using a strap based on 1650 strap plus 0 Tfaw, 0 Tfaw32 and 18 ACTRD. But I have a 460 with 560 bios. I can only hit 436H/s at 38W (GPU-Z measure) 1150/2030. What detailed settings are you using? |
|
|
|
Very nice hashrate but some seems electric value high and can graphic card more tired seems
I hope you like this new improved version Where is your ultra-mega-turbo-blaster-lastest improved version? |
|
|
|
|
Show Posts
