first, change the password to correct format for that pool "c=XLR" instead of " c=XLR_XEVAN" then try to remove all extra parameters except "algorithm": "xevan-mod", then increase intensity then hopefully profit  |
|
|
|
That would be "effective hashrate", its highly luck based, and not suitable for benchmarking. Although it could be nice to have to see how is you luck  Precisely why I want real data when mining. Benchmarking is done in a controlled environment free of extraneous variables like network latency, It's a theoretical value, essentialy a specification, like a car's fuel consumtion rating. I don't need the fuel consumtion rating displayed on my dashboard when I'm driving. I want real data, like fuel remaining and kms driven so I know how well it's performing vs the specification. I still have no idea why you would want theoretical data when real data is available. Theoretical data allows me to immediately detect if anything is affecting the hashrate while mining (by comparing to the benchmark) Be it overlocking, background process, other miner (GPU) or whatever and adjust accordingly |
|
|
|
But the bottom line, hashrate is a function of how many hashes can a processor calculate
Agree with your comments about pool stats, that is what I am aiming to replicate because it represents actual earnings. But CPU performance is static, once it's benchmarked why would you need/want continuous monitoring? I'm using an automated script (personal fork of Megaminer) for all benchmarking and mining. For benchmarking, I prefer to mine to a real pool, while also earning a little, without having to use "--benchmark" For some algos, the time until initial share can be very high (as in minutes), which makes for unnecessary long benchmark Sometimes the first share is submitted very fast (often happens for me with Lyra2z), and the reported rate, until the next share is submitted, is of 1 or 2 threads, which is very low and thus skews the benchmark It is also used in a watchdog to see that the miner really works as it should I'll consider that after I come up with a better way to report earnings. I'll have to figure out how pools convert a share to a hashrate then do the same calculation locally if I have all the variables. That would be a new data term that would probably be measured in hash rate and would be normalized based on share submission rate and share difficulty. The existing HS or KHS could then be used as you request and represent CPU performance. That would be "effective hashrate", its highly luck based, and not suitable for benchmarking. Although it could be nice to have to see how is you luck |
|
|
|
|
Strange behavior in latest version, noticed it once and not sure how to reproduce:
Megaminer switches to a coin which is profitable at the moment, interval finishes and it continues to mine same coin while showing it's profit as very high in the "Active Miners"
At the same time, in "Profits" screen, this coin is now significantly lower in profitability (way below the "PercentToSwitch")
Even after ending interval manually it continues to mine it, only restarting MegaMiner solves this
|
|
|
|
But the bottom line, hashrate is a function of how many hashes can a processor calculate
Agree with your comments about pool stats, that is what I am aiming to replicate because it represents actual earnings. But CPU performance is static, once it's benchmarked why would you need/want continuous monitoring? I'm using an automated script (personal fork of Megaminer) for all benchmarking and mining. For benchmarking, I prefer to mine to a real pool, while also earning a little, without having to use "--benchmark" For some algos, the time until initial share can be very high (as in minutes), which makes for unnecessary long benchmark Sometimes the first share is submitted very fast (often happens for me with Lyra2z), and the reported rate, until the next share is submitted, is of 1 or 2 threads, which is very low and thus skews the benchmark It is also used in a watchdog to see that the miner really works as it should |
|
|
|
On a sidenote, the feature I would love to see would be continuous hash rate reporting, not only when a share is found (which can take a while on some algos with current),
but reporting it continuously
Wouldn't we all. The problem is the locally calculated hashrate is completely artificial. To put this in perspective, while testing blakecoin with very high stratum diff the miner was reporting 150 MH/s but a single share submit resulted in the pool displaying 469 Mh/s. It remained at that rate until the share fell out of the sample window. So the pool reported hashrate went from 0 to 469 and back to zero every time a share was submitted. So I have to ask, what exactly do you expect from a continuous hashrate display that has no real connection to what the pool is seeing? I would like to see a measure that uses share submission rate and share difficulty so the miner can make calculations based on real data. Pools don't report a "more real" hashrate, they calculate an estimation based on amount of shares submitted and current difficulty. If you submit one share in 5 minutes, they don't have enough information to calculate real rate When difficulty is low enough to supply the pool with enough shares, the pool will show hashrate close to that which is calculated in the miner The lower the amount of shares submitted, the bigger role "luck" plays in the hashrate calculated by the pool But the bottom line, hashrate is a function of how many hashes can a processor calculate |
|
|
|
It doesn't make sense to me to put both but if that's what people want I'll do it. I'd like some
opinions from other users.
keep KH/s for backwards compatibility that is Given that another API change is coming is it worth it to reintroduce kH/s or just take the compatibility hit for both and get it over with? Current api is compatible with Ccminer, so I think changing it would break compatibility with many tools that people may use If you are reworking the api, then perhaps keeping existing one and activating it with a switch would be the "safe" way, but it would introduce additional code which I'm not sure you want to maintain. Perhaps set a cutoff date of when the old API will be discontinued? I personally mine on my own fork of MegaMiner ( https://github.com/yuzi-co/Megaminer) and changing the api is easy for me. On a sidenote, the feature I would love to see would be continuous hash rate reporting, not only when a share is found (which can take a while on some algos with current), but reporting it continuously |
|
|
|
Test last wtm pool file from master branch It looks the same... with coins.json . I dont think will work with manually added pool with LUX or BSD fro example... Now is getting all active coins from http://whattomine.com/coins.json, before was 55 from main page, now are 55 from main page and 44 from coins.json. wtm limits to 80 requests per minute currently there are 109 active coins on coins page and most are already listed on main change the condition to prevent api saturation and not process same coins twice: $WTMResponse.($_).status -eq "Active" -and ` #active
$WTMResponse.($_).listed -eq $false -and ` #not listed on main page
$WTMResponse.($_).lagging -eq $false -and `#up to date info
$WTMResponse.($_).testing -eq $false #verified formula and not a testing
|
|
|
|
For some reason I'm getting lots of duplicate shares on HOdl (windows avx2 version) First time I'm noticing this, and I'm pretty sure that didn't happen before 3.8.2 ********** cpuminer-opt 3.8.2.1 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX2 and SHA extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
CPU: Intel(R) Core(TM) i5-7600K CPU @ 3.80GHz.
SW built on Feb 17 2018 with GCC 5.3.1.
CPU features: SSE2 AES AVX AVX2.
SW features: SSE2 AES AVX AVX2.
Algo features: SSE2 AES AVX AVX2.
Start mining with AES AVX2.
[2018-02-18 20:55:13] Starting Stratum on stratum+tcp://hodl.EU.nicehash.com:3352
[2018-02-18 20:55:13] 4 miner threads started, using 'hodl' algorithm.
[2018-02-18 20:55:13] Stratum difficulty set to 4
[2018-02-18 20:55:16] Share submitted.
[2018-02-18 20:55:16] Accepted 1/1 (100%), 828 H, 512.19 H/s
[2018-02-18 20:55:18] Share submitted.
[2018-02-18 20:55:18] Accepted 2/2 (100%), 757 H, 532.64 H/s
[2018-02-18 20:55:21] Share submitted.
[2018-02-18 20:55:21] Accepted 3/3 (100%), 837 H, 560.42 H/s
[2018-02-18 20:55:23] Share submitted.
[2018-02-18 20:55:23] Accepted 4/4 (100%), 771 H, 503.08 H/s
[2018-02-18 20:55:23] Share submitted.
[2018-02-18 20:55:23] Rejected 1/5 (20.0%), 630 H, 459.92 H/s
[2018-02-18 20:55:23] reject reason: Duplicate share.
[2018-02-18 20:55:35] Share submitted.
[2018-02-18 20:55:35] Accepted 5/6 (83.3%), 816 H, 574.61 H/s
[2018-02-18 20:55:35] Share submitted.
[2018-02-18 20:55:35] Rejected 2/7 (28.6%), 723 H, 561.40 H/s
[2018-02-18 20:55:35] reject reason: Duplicate share.
[2018-02-18 20:55:35] Share submitted.
[2018-02-18 20:55:35] Rejected 3/8 (37.5%), 682 H, 552.16 H/s
[2018-02-18 20:55:35] reject reason: Duplicate share.
[2018-02-18 20:55:36] Share submitted.
[2018-02-18 20:55:36] Accepted 6/9 (66.7%), 510 H, 499.41 H/s
[2018-02-18 20:55:42] Share submitted.
[2018-02-18 20:55:42] Accepted 7/10 (70.0%), 967 H, 626.66 H/s
[2018-02-18 20:55:43] Share submitted.
[2018-02-18 20:55:43] Accepted 8/11 (72.7%), 739 H, 501.68 H/s
[2018-02-18 20:55:47] Share submitted.
[2018-02-18 20:55:47] Accepted 9/12 (75.0%), 1020 H, 654.92 H/s
[2018-02-18 20:55:47] Share submitted.
[2018-02-18 20:55:47] Share submitted.
[2018-02-18 20:55:47] Accepted 10/13 (76.9%), 529 H, 378.55 H/s
[2018-02-18 20:55:47] Rejected 4/14 (28.6%), 529 H, 378.55 H/s
[2018-02-18 20:55:47] reject reason: Duplicate share.
[2018-02-18 20:55:50] Share submitted.
[2018-02-18 20:55:50] Accepted 11/15 (73.3%), 462 H, 358.32 H/s
[2018-02-18 20:55:53] Share submitted.
[2018-02-18 20:55:53] Accepted 12/16 (75.0%), 944 H, 611.74 H/s
[2018-02-18 20:55:56] Share submitted.
[2018-02-18 20:55:56] Accepted 13/17 (76.5%), 902 H, 629.96 H/s
[2018-02-18 20:55:59] Share submitted.
[2018-02-18 20:55:59] Accepted 14/18 (77.8%), 800 H, 497.32 H/s
[2018-02-18 20:56:00] Share submitted.
[2018-02-18 20:56:00] Rejected 5/19 (26.3%), 800 H, 527.84 H/s
[2018-02-18 20:56:00] reject reason: Duplicate share.
[2018-02-18 20:56:09] Share submitted.
[2018-02-18 20:56:09] Accepted 15/20 (75.0%), 953 H, 495.64 H/s
[2018-02-18 20:56:10] Share submitted.
[2018-02-18 20:56:10] Accepted 16/21 (76.2%), 813 H, 480.12 H/s
[2018-02-18 20:56:11] Share submitted.
[2018-02-18 20:56:11] Accepted 17/22 (77.3%), 930 H, 627.86 H/s
[2018-02-18 20:56:23] Share submitted.
[2018-02-18 20:56:23] Accepted 18/23 (78.3%), 903 H, 604.42 H/s
[2018-02-18 20:56:26] Share submitted.
[2018-02-18 20:56:26] Accepted 19/24 (79.2%), 963 H, 634.86 H/s
[2018-02-18 20:56:28] Share submitted.
[2018-02-18 20:56:28] Accepted 20/25 (80.0%), 885 H, 581.31 H/s
[2018-02-18 20:56:38] Share submitted.
[2018-02-18 20:56:38] Accepted 21/26 (80.8%), 983 H, 647.70 H/s
[2018-02-18 20:56:41] Share submitted.
[2018-02-18 20:56:41] Accepted 22/27 (81.5%), 836 H, 575.98 H/s
[2018-02-18 20:56:50] Share submitted.
[2018-02-18 20:56:50] Accepted 23/28 (82.1%), 1017 H, 551.69 H/s
[2018-02-18 20:56:55] Share submitted.
[2018-02-18 20:56:55] Accepted 24/29 (82.8%), 850 H, 580.15 H/s
[2018-02-18 20:56:56] Share submitted.
[2018-02-18 20:56:57] Accepted 25/30 (83.3%), 589 H, 453.69 H/s
[2018-02-18 20:56:59] Share submitted.
[2018-02-18 20:56:59] Accepted 26/31 (83.9%), 838 H, 504.05 H/s
[2018-02-18 20:57:02] Share submitted.
[2018-02-18 20:57:02] Accepted 27/32 (84.4%), 901 H, 597.33 H/s
[2018-02-18 20:57:04] Share submitted.
[2018-02-18 20:57:04] Accepted 28/33 (84.8%), 829 H, 592.27 H/s
[2018-02-18 20:57:05] Share submitted.
[2018-02-18 20:57:05] Accepted 29/34 (85.3%), 828 H, 580.02 H/s
[2018-02-18 20:57:05] Share submitted.
[2018-02-18 20:57:06] Rejected 6/35 (17.1%), 742 H, 556.84 H/s
[2018-02-18 20:57:06] reject reason: Duplicate share.
[2018-02-18 20:57:08] Share submitted.
[2018-02-18 20:57:08] Accepted 30/36 (83.3%), 760 H, 466.53 H/s
[2018-02-18 20:57:22] Share submitted.
[2018-02-18 20:57:22] Accepted 31/37 (83.8%), 906 H, 620.70 H/s
[2018-02-18 20:57:32] Share submitted.
[2018-02-18 20:57:32] Accepted 32/38 (84.2%), 804 H, 559.32 H/s
[2018-02-18 20:57:33] Share submitted.
[2018-02-18 20:57:33] Rejected 7/39 (17.9%), 778 H, 553.00 H/s
[2018-02-18 20:57:33] reject reason: Duplicate share.
[2018-02-18 20:57:39] Share submitted.
[2018-02-18 20:57:39] Accepted 33/40 (82.5%), 883 H, 570.50 H/s
[2018-02-18 20:57:40] Share submitted.
[2018-02-18 20:57:40] Accepted 34/41 (82.9%), 881 H, 538.16 H/s
[2018-02-18 20:57:43] Share submitted.
[2018-02-18 20:57:43] Accepted 35/42 (83.3%), 777 H, 520.58 H/s
[2018-02-18 20:57:48] Share submitted.
[2018-02-18 20:57:48] Accepted 36/43 (83.7%), 764 H, 462.16 H/s
[2018-02-18 20:57:52] Share submitted.
[2018-02-18 20:57:52] Accepted 37/44 (84.1%), 803 H, 562.67 H/s
[2018-02-18 20:57:53] Share submitted.
[2018-02-18 20:57:53] Accepted 38/45 (84.4%), 564 H, 420.31 H/s
[2018-02-18 20:57:56] Share submitted.
[2018-02-18 20:57:56] Accepted 39/46 (84.8%), 781 H, 511.72 H/s
[2018-02-18 20:57:57] Share submitted.
[2018-02-18 20:57:57] Rejected 8/47 (17.0%), 719 H, 490.55 H/s
[2018-02-18 20:57:57] reject reason: Duplicate share.
[2018-02-18 20:58:02] Share submitted.
[2018-02-18 20:58:02] Accepted 40/48 (83.3%), 923 H, 607.02 H/s
[2018-02-18 20:58:05] Share submitted.
[2018-02-18 20:58:05] Accepted 41/49 (83.7%), 842 H, 594.09 H/s
[2018-02-18 20:58:11] Share submitted.
[2018-02-18 20:58:11] Accepted 42/50 (84.0%), 899 H, 572.50 H/s
[2018-02-18 20:58:12] Share submitted.
[2018-02-18 20:58:12] Accepted 43/51 (84.3%), 821 H, 600.97 H/s
[2018-02-18 20:58:13] Stratum difficulty set to 8
[2018-02-18 20:58:14] Share submitted.
[2018-02-18 20:58:14] Accepted 44/52 (84.6%), 1024 H, 663.72 H/s
[2018-02-18 20:58:17] Share submitted.
[2018-02-18 20:58:17] Accepted 45/53 (84.9%), 837 H, 558.85 H/s
[2018-02-18 20:58:22] Share submitted.
[2018-02-18 20:58:22] Accepted 46/54 (85.2%), 771 H, 499.49 H/s
[2018-02-18 20:58:22] Share submitted.
[2018-02-18 20:58:23] Rejected 9/55 (16.4%), 733 H, 493.61 H/s
[2018-02-18 20:58:23] reject reason: Duplicate share.
[2018-02-18 20:58:23] Share submitted.
[2018-02-18 20:58:23] Accepted 47/56 (83.9%), 548 H, 426.37 H/s
[2018-02-18 20:58:27] Share submitted.
[2018-02-18 20:58:27] Accepted 48/57 (84.2%), 801 H, 531.96 H/s
[2018-02-18 20:58:29] Share submitted.
[2018-02-18 20:58:29] Accepted 49/58 (84.5%), 745 H, 499.57 H/s
[2018-02-18 20:58:39] Share submitted.
[2018-02-18 20:58:39] Accepted 50/59 (84.7%), 946 H, 549.25 H/s
[2018-02-18 20:58:42] Share submitted.
[2018-02-18 20:58:42] Accepted 51/60 (85.0%), 934 H, 580.80 H/s
[2018-02-18 20:58:56] Share submitted.
[2018-02-18 20:58:57] Accepted 52/61 (85.2%), 854 H, 535.76 H/s
[2018-02-18 20:59:07] Share submitted.
[2018-02-18 20:59:07] Accepted 53/62 (85.5%), 934 H, 531.44 H/s
[2018-02-18 20:59:14] Share submitted.
[2018-02-18 20:59:14] Accepted 54/63 (85.7%), 813 H, 558.06 H/s
[2018-02-18 20:59:23] Share submitted.
[2018-02-18 20:59:23] Accepted 55/64 (85.9%), 831 H, 562.15 H/s
[2018-02-18 20:59:23] Share submitted.
[2018-02-18 20:59:23] Rejected 10/65 (15.4%), 709 H, 538.59 H/s
[2018-02-18 20:59:23] reject reason: Duplicate share.
[2018-02-18 20:59:46] Share submitted.
[2018-02-18 20:59:46] Accepted 56/66 (84.8%), 1036 H, 618.62 H/s
[2018-02-18 20:59:48] Share submitted.
[2018-02-18 20:59:48] Accepted 57/67 (85.1%), 1036 H, 635.54 H/s
[2018-02-18 20:59:49] Share submitted.
[2018-02-18 20:59:49] Accepted 58/68 (85.3%), 972 H, 612.73 H/s
[2018-02-18 21:00:04] Share submitted.
[2018-02-18 21:00:04] Accepted 59/69 (85.5%), 854 H, 576.46 H/s
[2018-02-18 21:00:09] Share submitted.
[2018-02-18 21:00:09] Accepted 60/70 (85.7%), 780 H, 488.07 H/s EDIT: I think it's Nicehash only issue Mining on another pool seems fine ********** cpuminer-opt 3.8.2.1 ***********
A CPU miner with multi algo support and optimized for CPUs
with AES_NI and AVX2 and SHA extensions.
BTC donation address: 12tdvfF7KmAsihBXQXynT6E6th2c2pByTT
CPU: Intel(R) Core(TM) i5-7600K CPU @ 3.80GHz.
SW built on Feb 17 2018 with GCC 5.3.1.
CPU features: SSE2 AES AVX AVX2.
SW features: SSE2 AES AVX AVX2.
Algo features: SSE2 AES AVX AVX2.
Start mining with AES AVX2.
[2018-02-18 21:30:00] Starting Stratum on stratum+tcp://roi.suprnova.cc:4699
[2018-02-18 21:30:00] 4 miner threads started, using 'hodl' algorithm.
[2018-02-18 21:30:01] Stratum difficulty set to 8
[2018-02-18 21:30:20] Share submitted.
[2018-02-18 21:30:20] Accepted 1/1 (100%), 880 H, 455.67 H/s
[2018-02-18 21:30:23] Share submitted.
[2018-02-18 21:30:23] Accepted 2/2 (100%), 764 H, 462.02 H/s
[2018-02-18 21:30:31] Share submitted.
[2018-02-18 21:30:31] Accepted 3/3 (100%), 919 H, 538.87 H/s
[2018-02-18 21:31:00] Stratum difficulty set to 14.5455
[2018-02-18 21:31:04] Share submitted.
[2018-02-18 21:31:04] Accepted 4/4 (100%), 904 H, 561.84 H/s
[2018-02-18 21:31:06] Share submitted.
[2018-02-18 21:31:06] Accepted 5/5 (100%), 972 H, 607.93 H/s
[2018-02-18 21:31:55] Stratum difficulty set to 4.40771
[2018-02-18 21:32:03] Share submitted.
[2018-02-18 21:32:03] Accepted 6/6 (100%), 813 H, 446.92 H/s
[2018-02-18 21:32:08] Share submitted.
[2018-02-18 21:32:08] Share submitted.
[2018-02-18 21:32:08] Accepted 7/7 (100%), 554 H, 379.70 H/s
[2018-02-18 21:32:08] Accepted 8/8 (100%), 554 H, 379.70 H/s
[2018-02-18 21:32:10] Share submitted.
[2018-02-18 21:32:10] Accepted 9/9 (100%), 608 H, 384.08 H/s
[2018-02-18 21:32:15] Share submitted.
[2018-02-18 21:32:16] Accepted 10/10 (100%), 748 H, 516.28 H/s
[2018-02-18 21:32:18] Share submitted.
[2018-02-18 21:32:18] Accepted 11/11 (100%), 540 H, 369.01 H/s
[2018-02-18 21:32:18] Share submitted.
[2018-02-18 21:32:18] Accepted 12/12 (100%), 452 H, 361.97 H/s
[2018-02-18 21:32:23] Share submitted.
[2018-02-18 21:32:23] Accepted 13/13 (100%), 998 H, 566.35 H/s
[2018-02-18 21:32:26] Share submitted.
[2018-02-18 21:32:26] Accepted 14/14 (100%), 843 H, 508.53 H/s
[2018-02-18 21:32:28] Share submitted.
[2018-02-18 21:32:28] Accepted 15/15 (100%), 719 H, 464.78 H/s
[2018-02-18 21:32:33] Share submitted.
[2018-02-18 21:32:33] Accepted 16/16 (100%), 792 H, 441.48 H/s
[2018-02-18 21:32:41] Share submitted.
[2018-02-18 21:32:42] Accepted 17/17 (100%), 772 H, 502.26 H/s
[2018-02-18 21:32:44] Share submitted.
[2018-02-18 21:32:44] Accepted 18/18 (100%), 683 H, 421.64 H/s
[2018-02-18 21:32:50] Stratum difficulty set to 10.4946
[2018-02-18 21:32:57] Share submitted.
[2018-02-18 21:32:57] Accepted 19/19 (100%), 1038 H, 650.49 H/s
[2018-02-18 21:32:58] Share submitted.
[2018-02-18 21:32:58] Accepted 20/20 (100%), 843 H, 570.27 H/s
[2018-02-18 21:33:14] Share submitted.
[2018-02-18 21:33:14] Accepted 21/21 (100%), 922 H, 525.04 H/s
[2018-02-18 21:33:34] Share submitted.
[2018-02-18 21:33:34] Accepted 22/22 (100%), 971 H, 594.49 H/s
[2018-02-18 21:33:41] Share submitted.
[2018-02-18 21:33:41] Accepted 23/23 (100%), 918 H, 571.24 H/s
[2018-02-18 21:34:02] Share submitted.
[2018-02-18 21:34:02] Accepted 24/24 (100%), 996 H, 614.81 H/s
[2018-02-18 21:34:05] Share submitted.
[2018-02-18 21:34:05] Accepted 25/25 (100%), 760 H, 441.58 H/s
[2018-02-18 21:34:08] Share submitted.
[2018-02-18 21:34:08] Accepted 26/26 (100%), 841 H, 557.85 H/s
[2018-02-18 21:34:18] Share submitted.
[2018-02-18 21:34:18] Accepted 27/27 (100%), 886 H, 546.23 H/s
[2018-02-18 21:34:29] Share submitted.
[2018-02-18 21:34:29] Accepted 28/28 (100%), 869 H, 577.68 H/s
[2018-02-18 21:34:30] Share submitted.
[2018-02-18 21:34:31] Accepted 29/29 (100%), 620 H, 450.94 H/s
[2018-02-18 21:34:31] Share submitted.
[2018-02-18 21:34:31] Accepted 30/30 (100%), 476 H, 409.03 H/s |
|
|
|
Hello, here are some results from myr-gr with 3.8.1.1 and 3.8.0.1, same Ryzen 1800x with Win 8.1 64-bit, cpuminer-avx2-sha:
But I have reproduced that neoscrypt is broken on Windows, it works on Linux I will investigate. Neoscrypt is broken since the cross-compile, I believe you said that you will have to rewrite it, but since its not very useful on cpu, its low on the priority list ) |
|
|
|
And not a single one of you mentioned which operating system you are using. How 'bout it?
Windows 10 ps. judging from "F:\Miners\CPU>", guytechie also uses windows |
|
|
|
With 3.8.1, trying to mine xevan it would start, but then exits without any errors. I tried on different pools, and same behavior. F:\Miners\CPU>cpuminer-avx2-sha.exe -a xevan -o stratum+tcp://xevan.mine.zpool.ca:3739 -u 1MkmBHDjonAFXui6JEx9ZmEemfMtUo9Cmu -p c=BTC
********** cpuminer-opt 3.8.1 ***********
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 Threadripper 1950X 16-Core Processor .
SW built on Feb 7 2018 with GCC 5.3.1.
CPU features: SSE2 AES AVX AVX2 SHA.
SW features: SSE2 AES AVX AVX2 SHA.
Algo features: SSE2 AES AVX AVX2.
Start mining with AES AVX2.
[2018-02-08 23:50:41] Starting Stratum on stratum+tcp://xevan.mine.zpool.ca:3739
[2018-02-08 23:50:41] 32 miner threads started, using 'xevan' algorithm.
[2018-02-08 23:50:41] Stratum difficulty set to 0.062
[2018-02-08 23:50:47] xevan block 223318, diff 39.822
F:\Miners\CPU>
This is also happening for bitcore. I don't know what other algos this could be happening to since I didn't test it all. I do know that yescrypt, m7m, cryptonight, and lyra2z is working fine though. 3.8.1 crashes also on x16r and x17. didnt test others yet |
|
|
|
cpuminer-opt-3.8.0.1 fixes X16R AVX2 low hashrate. https://github.com/JayDDee/cpuminer-opt/releases/tag/v3.8.0.1There were actually 2 bugs. The first one prevented any shares from being submitted from lanes 1 to 3 which hid the second bug that caused only rejects from those lanes. As a result only the valid shares were submitted and the only symptom was the low hashrate reported by the pool. A strange coincidence. Thanks to 4ward for noticing and reporting the problem. Significant improvement on pools side now Thank you for the swift fix ) |
|
|
|
cpuminer-opt-3.8.0 released. https://github.com/JayDDee/cpuminer-opt/releases/tag/v3.8.04way no longer a seperate feature, included in AVX2. Added x16r algo for Ravencoin, anime algo for Animecoin. More 4way optimizations for X13 and up. Tweaked CPU affinity to better support more than 64 CPUs. Fixed compile problem on some old AMD CPUs. This release is a major milestone for cpuminer-opt. It essentially marks the end of 4way phase 1. 15 of the 17 functions in X17 have some form of optimization. Only fugue and whirlpool still use unoptimized code and 4 way seems impossible on these functions using SIMD. for some reason X16r shows about 4x the hashrate of the official cpuminer (by Tpuvot), while actually delivering lower hashrate and sharerate on the pool side p.s. dropped a penny in the ETH jar Thanks for the tip. Your report about hash rate is scary because it's hard to verify. x16r by it's nature has a very volatile hash rate and Suprnova has been notorious for displaying incorrect hash rates. There is no difference in the miner-side hashrate calculation for x16r. I made a change for 4way to account for 4 nonces per iteration but it applies to all 4way algos and seems to be accurate. It'll need more data from other users to determine if there is a problem with hashrate calculation. Edit: hash rate for x16r is more volatile with opt vs multi due to the mix of optimized and unoptimized hash functions. X16r can theoretically run the same function 16 times. If it's an unoptimized function the hash rate with opt wil be the same as multi. But if it's a highly optimized function the hash rate gain will be higher than average. So I finally got some time to test this and confirm the results I saw I have mined to 2 wallets on http://pool.threeeyed.info/Running 2 miners in parallel, with 2 threads each, on 4 core cpu, with manually defined affinity in task manager to make sure they use separate cores Running for 2 hours with no interruptions, here is the results multi gave double the profit, and reported more or less correct speed opt reported speed was about 4 times higher that the received speed on pool cpuminer-opt 3.8.0: Screenshot: http://prntscr.com/iafztrMiner output: https://text-share.com/view/e95290d4Pool link: http://pool.threeeyed.info/?address=RMuoJFg2qDSxEaDaCZG24Yhn3k99gW6SkFcpuminer-multi-1.3.3 Screenshot: http://prntscr.com/iafzkkMiner output: https://text-share.com/view/59a010b3Pool link: http://pool.threeeyed.info/?address=RJmz1bAtpa4hXrX7LC82cVikoB4gpd5L52 |
|
|
|
Do anybody know the lyra2z hashrate for "core i5 6400"?
i5 7600k @ 4.5Ghz gives ~500kh/s So I would guess something like ~450kh/s Can I ask, after monero fly away with Diff, now more profitable LYRA2 ? Lyra2z, Yescrypt, sometimes HODL on NiceHash, Yenten, HPP coin This is in general the algos that can still get some profit on a CPU |
|
|
|
Do anybody know the lyra2z hashrate for "core i5 6400"?
i5 7600k @ 4.5Ghz gives ~500kh/s So I would guess something like ~450kh/s |
|
|
|
I saw "goodbitprofit" bat file in recent post.
I have questions about -etht 1000 settings and -estale 1.
For that -etht 1000 I saw in one you tube video I can not remember about what it was, but from that time I am using that command, and I am not shure for what is it. But after using it my rigs working normal. About another -estale 1 I am not using it. I was also tried several different setups, and finally I find this to work for me. It seems that some setups are not working on another setups, how I see. Depending from memories, drivers, type of rasers, Windows,... try reading Readme file -etht Time period between Ethereum HTTP requests for new job in solo mode, in milliseconds. Default value is 200ms. It's useless for pool mining )) |
|
|
|
Having a strange issue when mining Skunk on RX 480 + Blockchain drivers
After initialization, the GPU speed drops to ~600 instead of working on the max 1250MHz
Obviously the hashrate suffers and is about 15 instead on 19+
Any ideas why is this happening or how to force the full speed?
Sounds like overheating problem The fan in the above scenario is running on almost silent and the temperatures are pretty low And it works fine on all other miners including dual mining (which heats it up way more) Its possible that it started after installing the Blockchain drivers (previously was running on latest drivers in Compute mode), I need to try reinstalling them... |
|
|
|
|
Show Posts
