Hi! I'm new to NemosMiner but I have used SniffDogMiner and of course MultiPoolMiner, so not totally newbie. My question is this (and sorry if it's been asked): MPM, as far as I remember, used 2-3 different miners for some algorithms to determine the best one. Isn't this the case in NM? Because I'm finishing a benchmark now and only see 1 miner tested per algorithm. Also, I had to disable timetravel and x16r during benchmarks, I guess both of them were crashing. Is there anything I can do about it? Maybe another miner or something? Btw, my rig is a 9x1070 one. Thanks for any help!  timetravel and x16r are worthless so remove NM is already setup to use only the most optimized miner for the particular algo so thats normal to only see one miner per algo x17/phi are making all the money these days for us
|
|
|
Been away from Nemos for some time hunting the most profitable coins. since i wont have time to do that any more, can someone please report 24h earnings with 6*1080ti on ahashpoolplus/zpoolplus? Thanks!
About 0.00169 BTC (1.69 mBTC)
|
|
|
2.5.1 switching like on crack on zpoolplus.bat like 3-4 times per hour, cant figure out is that affecting earnings. tried with 5% and 240 interval but doesn't seem to help. any ideas? "date","algo","wallet","username","Stratum" "1.3.2018. 12:15:16 ","Skein","addres","nemo","stratum+tcp://skein.mine.zpool.ca:4933" "1.3.2018. 12:25:26 ","Bitcore","addres","nemo","stratum+tcp://bitcore.mine.zpool.ca:3556" "1.3.2018. 12:35:36 ","Skunk","addres","nemo","stratum+tcp://skunk.mine.zpool.ca:8433" "1.3.2018. 12:45:46 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "1.3.2018. 12:55:56 ","Poly","addres","nemo","stratum+tcp://polytimos.mine.zpool.ca:8463" "1.3.2018. 1:06:09 ","Groestl","1QGADhdMRpp9Pk5u5zG1TrHKRrdK5R81TE","nemo","stratum+tcp://groestl.mine.zpool.ca:5333" "1.3.2018. 1:16:20 ","Nist5","addres","nemo","stratum+tcp://nist5.mine.zpool.ca:3833" "1.3.2018. 1:26:32 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233" "1.3.2018. 1:36:43 ","Lyra2RE2","addres","nemo","stratum+tcp://lyra2v2.mine.zpool.ca:4533" "1.3.2018. 1:46:52 ","Equihash","addres","nemo","" "1.3.2018. 1:57:03 ","Lbry","addres","nemo","stratum+tcp://lbry.mine.zpool.ca:3334" "1.3.2018. 2:07:42 ","C11","addres","nemo","stratum+tcp://c11.mine.zpool.ca:3573" "1.3.2018. 2:29:59 ","Blake2s","addres","nemo","stratum+tcp://blake2s.mine.zpool.ca:5766" "1.3.2018. 2:40:08 ","Lyra2z","addres","nemo","stratum+tcp://lyra2z.mine.zpool.ca:4553" "1.3.2018. 2:50:19 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "1.3.2018. 3:00:30 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "1.3.2018. 3:10:41 ","Sib","addres","nemo","stratum+tcp://sib.mine.zpool.ca:5033" "1.3.2018. 3:20:53 ","X11evo","addres","nemo","stratum+tcp://x11evo.mine.zpool.ca:3553" "1.3.2018. 3:31:03 ","MyriadGroestl","addres","nemo","stratum+tcp://myr-gr.mine.zpool.ca:5433" "1.3.2018. 3:41:15 ","Tribus","addres","nemo","stratum+tcp://tribus.mine.zpool.ca:8533" "1.3.2018. 3:51:26 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433" "1.3.2018. 4:01:37 ","Blakecoin","addres","nemo","stratum+tcp://blakecoin.mine.zpool.ca:5743" "1.3.2018. 4:11:47 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "1.3.2018. 5:19:37 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "1.3.2018. 5:51:04 ","Lyra2RE2","addres","nemo","stratum+tcp://lyra2v2.mine.zpool.ca:4533" "1.3.2018. 6:16:28 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "1.3.2018. 7:00:05 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "1.3.2018. 7:31:59 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "1.3.2018. 9:04:02 ","Tribus","addres","nemo","stratum+tcp://tribus.mine.zpool.ca:8533" "1.3.2018. 9:11:15 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "1.3.2018. 11:01:30 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "1.3.2018. 11:26:54 ","Skein","addres","nemo","stratum+tcp://skein.mine.zpool.ca:4933" "1.3.2018. 11:40:11 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433" "2.3.2018. 12:17:42 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "2.3.2018. 1:19:30 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "2.3.2018. 1:50:58 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "2.3.2018. 3:04:52 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433" "2.3.2018. 3:18:09 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "2.3.2018. 4:38:07 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "2.3.2018. 6:28:25 ","Tribus","addres","nemo","stratum+tcp://tribus.mine.zpool.ca:8533" "2.3.2018. 6:59:53 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "2.3.2018. 8:01:40 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "2.3.2018. 9:33:47 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "2.3.2018. 10:53:48 ","Tribus","addres","nemo","stratum+tcp://tribus.mine.zpool.ca:8533" "2.3.2018. 11:19:12 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "2.3.2018. 1:15:36 ","Xevan","134bw4oTorEJUUVFhokDQDfNqTs7rBMNYy","MrPlus","stratum+tcp://xevan.mine.zpool.ca:3739" "2.3.2018. 1:16:45 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "2.3.2018. 1:48:14 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "2.3.2018. 3:02:10 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "2.3.2018. 4:10:04 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "2.3.2018. 4:47:38 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "2.3.2018. 5:25:10 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "2.3.2018. 7:27:36 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "2.3.2018. 8:35:30 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "2.3.2018. 9:06:59 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "2.3.2018. 9:38:29 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233" "2.3.2018. 10:03:54 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "2.3.2018. 10:47:32 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233" "2.3.2018. 11:25:31 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "2.3.2018. 11:57:01 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "3.3.2018. 1:10:59 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "3.3.2018. 1:55:08 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "3.3.2018. 2:20:34 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433" "3.3.2018. 2:46:00 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233" "3.3.2018. 3:29:37 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "3.3.2018. 4:25:22 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233" "3.3.2018. 5:21:08 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "3.3.2018. 6:47:13 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "3.3.2018. 7:49:02 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "3.3.2018. 8:32:52 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "3.3.2018. 10:17:09 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "3.3.2018. 11:37:12 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "3.3.2018. 12:39:05 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233" "3.3.2018. 1:16:42 ","Xevan","1MsrCoAt8qM53HUMsUxvy9gMj3QVbHLazH","aaronsace","stratum+tcp://xevan.mine.zpool.ca:3739" "3.3.2018. 1:17:50 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "3.3.2018. 3:40:25 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "3.3.2018. 4:48:17 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "3.3.2018. 6:08:22 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "3.3.2018. 6:58:03 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233" "3.3.2018. 7:47:44 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "3.3.2018. 8:19:15 ","Equihash","addres","nemo","" "3.3.2018. 9:15:02 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "3.3.2018. 10:04:43 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233" "3.3.2018. 10:42:18 ","Lyra2z","addres","nemo","stratum+tcp://lyra2z.mine.zpool.ca:4553" "3.3.2018. 11:13:48 ","Equihash","addres","nemo","" "3.3.2018. 11:45:20 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "4.3.2018. 12:35:06 ","Equihash","addres","nemo","" "4.3.2018. 2:07:24 ","Lyra2z","addres","nemo","stratum+tcp://lyra2z.mine.zpool.ca:4553" "4.3.2018. 2:32:52 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433" "4.3.2018. 4:35:27 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "4.3.2018. 5:31:14 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "4.3.2018. 7:28:56 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "4.3.2018. 8:42:55 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233" "4.3.2018. 9:14:25 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "4.3.2018. 10:04:10 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233" "4.3.2018. 10:47:55 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "4.3.2018. 12:32:18 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233" "4.3.2018. 1:15:57 ","Phi","134bw4oTorEJUUVFhokDQDfNqTs7rBMNYy","MrPlus","stratum+tcp://phi.mine.zpool.ca:8333" "4.3.2018. 1:23:12 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "4.3.2018. 3:31:52 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "4.3.2018. 4:15:31 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233" "4.3.2018. 5:05:16 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "4.3.2018. 5:30:42 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "4.3.2018. 6:26:31 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "4.3.2018. 7:16:14 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "4.3.2018. 8:18:09 ","NeoScrypt","addres","nemo","stratum+tcp://neoscrypt.mine.zpool.ca:4233" "4.3.2018. 8:55:46 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "4.3.2018. 9:33:24 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "4.3.2018. 9:58:49 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433" "4.3.2018. 10:18:24 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "4.3.2018. 10:55:59 ","C11","addres","nemo","stratum+tcp://c11.mine.zpool.ca:3573" "4.3.2018. 11:15:21 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433" "4.3.2018. 11:28:39 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "5.3.2018. 12:30:30 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "5.3.2018. 1:32:20 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433" "5.3.2018. 2:22:01 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "5.3.2018. 3:23:51 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433" "5.3.2018. 3:43:14 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "5.3.2018. 4:32:56 ","Lyra2z","addres","nemo","stratum+tcp://lyra2z.mine.zpool.ca:4553" "5.3.2018. 4:52:19 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "5.3.2018. 6:00:14 ","Hsr","addres","nemo","stratum+tcp://hsr.mine.zpool.ca:7433" "5.3.2018. 6:44:38 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "5.3.2018. 7:22:12 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "5.3.2018. 9:37:13 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "5.3.2018. 9:50:30 ","Bitcore","addres","nemo","stratum+tcp://bitcore.mine.zpool.ca:3556" "5.3.2018. 10:22:02 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "5.3.2018. 11:42:34 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "5.3.2018. 12:20:48 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "5.3.2018. 1:22:41 ","X17","1QGADhdMRpp9Pk5u5zG1TrHKRrdK5R81TE","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "5.3.2018. 1:23:52 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "5.3.2018. 3:32:30 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "5.3.2018. 5:10:46 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "5.3.2018. 5:36:12 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "5.3.2018. 6:56:18 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "5.3.2018. 7:12:25 ","Xevan","addres","nemo","stratum+tcp://xevan.mine.zpool.ca:3739" "5.3.2018. 7:13:03 ","Tribus","addres","nemo","stratum+tcp://tribus.mine.zpool.ca:8533" "5.3.2018. 7:17:40 ","Tribus","addres","nemo","stratum+tcp://tribus.mine.zpool.ca:8533" "5.3.2018. 7:18:49 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333" "5.3.2018. 8:00:16 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "5.3.2018. 8:17:32 ","X17","1MsrCoAt8qM53HUMsUxvy9gMj3QVbHLazH","aaronsace","stratum+tcp://x17.mine.zpool.ca:3737" "5.3.2018. 8:18:41 ","X17","addres","nemo","stratum+tcp://x17.mine.zpool.ca:3737" "5.3.2018. 9:16:15 ","Phi","addres","nemo","stratum+tcp://phi.mine.zpool.ca:8333"
Looks fine
|
|
|
I installed 2.4.2 on 2 rigs and one of them is rebooting repeatedly now every few hours, and the other is fine. Very odd behavior.. Had to revert back to 2.3.. Anyone else have this issue? No errors in the event viewer, nothing in whocrashed (no minidumps or bluescreens), and log files are not helpful. The rig was super stable with 2.3.1...
Probably pushing your power limits when hashing a particular algo. Try backing off power limit 10% in MSI AfterBurner. Also time to upgrade to 2.5
|
|
|
Well the second 24 hour wasn't as nice.... 2/29/2018 Nicehash 0.01319923 while my 62 GPU on X17/AHashPool did 0.013345! Since the 72 gpu should have 14.8% better I would have expected 0.015320 if I was on AHashPool.
So after 48 hours, if left on X17/AHashPool we would be around 0.028557, but currently we are 0.02744565... Not the end of the world, .001 LESS on NiceHash so far after 48 hour test. Definitely not enough to make me cancel the testing so we'll continue the tests, keeping the 62 gpu on X17/AHashPool and 72 gpu on NiceHash to see if we just had a bad day on NiceHash..... Do you still recommend -ActiveMinerGainPct 5 for AhashPoolPlus? I prefer 120 interval and 5 Percent
|
|
|
FULL 12 RIG 72 GPU NICEHASH TESTOk guys, I've switched one entire farm (72 GPUs, 12 rigs) over to NiceHash (2.0.1.11) - 48 HOUR TEST!!!! https://imgur.com/a/vNodgLast 3 Payouts on AHashPool (Use to be 0.021 at its peak) 19h ago 0.01532754 330b3de0606d1257621e51301da726f8ca02... 43h ago 0.01419105 87ce1e684a440868ea347bcde8766b5ac7f8... 2d ago 0.01409336 67db48c92b113c2c98fc62461144ad8399bd... Lets see how it plays out compared to my AHashPoolPlus 62 GPU Farm First 24 hours (2/28/2018): Farm #1 (62 gpu) which is still using NemosMiner 2.5/NPlusMiner 1.3.3 on AhashPoolPlus produced .011531 BTC Farm #2 (72 gpu) which is on NiceHash Miner v2.0.1.11 produced .01424642 BTC Farm #2 Typically produces on the high side 14.8% better revenue, so if the 72 gpu farm was on AHashPool I would have expected .013237 best case .01424642 - .013237 = 7.6% better revenue on NiceHash! Lets see how the next 24 play out.... Well the second 24 hour wasn't as nice.... 2/29/2018 Nicehash 0.01319923 while my 62 GPU on X17/AHashPool did 0.013345! Since the 72 gpu should have 14.8% better I would have expected 0.015320 if I was on AHashPool. So after 48 hours, if left on X17/AHashPool we would be around 0.028557, but currently we are 0.02744565... Not the end of the world, .001 LESS on NiceHash so far after 48 hour test. Definitely not enough to make me cancel the testing so we'll continue the tests, keeping the 62 gpu on X17/AHashPool and 72 gpu on NiceHash to see if we just had a bad day on NiceHash.....
|
|
|
Did something happen with mining this week? My 3 1070 Ti's were making a measely $12 a day and now it's closer to $5? (total) (AHashPool)
Did difficulty skyrocket again? Or is this because prices of coins remained still?
Should be $6.00-$6.50 for 3 (1070ti) on AHashPool or NiceHash currently. Has been this way for many weeks. Impossible for 3 cards to make $12/day for the last month!
|
|
|
FULL 12 RIG 72 GPU NICEHASH TESTOk guys, I've switched one entire farm (72 GPUs, 12 rigs) over to NiceHash (2.0.1.11) - 48 HOUR TEST!!!! https://imgur.com/a/vNodgLast 3 Payouts on AHashPool (Use to be 0.021 at its peak) 19h ago 0.01532754 330b3de0606d1257621e51301da726f8ca02... 43h ago 0.01419105 87ce1e684a440868ea347bcde8766b5ac7f8... 2d ago 0.01409336 67db48c92b113c2c98fc62461144ad8399bd... Lets see how it plays out compared to my AHashPoolPlus 62 GPU Farm First 24 hours (2/28/2018): Farm #1 (62 gpu) which is still using NemosMiner 2.5/NPlusMiner 1.3.3 on AhashPoolPlus produced .011531 BTC Farm #2 (72 gpu) which is on NiceHash Miner v2.0.1.11 produced .01424642 BTC Farm #2 Typically produces on the high side 14.8% better revenue, so if the 72 gpu farm was on AHashPool I would have expected .013237 best case .01424642 - .013237 = 7.6% better revenue on NiceHash! Lets see how the next 24 play out....
|
|
|
30% increase in performance with lower power consumption. The price will come down. That is a huge assumption. Lets just say it does 30% better. Its far better to buy today at $900 for a 1080ti and mine for 4 months, covering about $400 of that $900 cost. By July my 1080ti will be at $500 cost, while you are purchasing that shiny new 2080 for $1500 (3 times the cost) for 30% more hashing power. That is if you are able to get your hands on 4-6 of them to build a mining rig while tens of thousand of other miners are trying to.
|
|
|
FULL 12 RIG 72 GPU NICEHASH TESTOk guys, I've switched one entire farm (72 GPUs, 12 rigs) over to NiceHash (2.0.1.11) - 48 HOUR TEST!!!! https://imgur.com/a/vNodgLast 3 Payouts on AHashPool (Use to be 0.021 at its peak) 19h ago 0.01532754 330b3de0606d1257621e51301da726f8ca02... 43h ago 0.01419105 87ce1e684a440868ea347bcde8766b5ac7f8... 2d ago 0.01409336 67db48c92b113c2c98fc62461144ad8399bd... Lets see how it plays out compared to my AHashPoolPlus 62 GPU Farm How about running the 72 GPU farm on NiceHash for 48 hours and then on AHashPoolPlus for 48 hours? You have to run exact same builds at the exact same time on each platform to have any kind of accurate results.  I have daily BTC history for this particular farm going back months! Use to average 0.021 BTC, lately its been 0.014-0.015. Last was 0.0133 just after switchover. NiceHash running 48 hours if it can avg >0.0145 it will have made MORE than NemosMiner/NPlusMiner 1.3.3 on AHashPoolPlus. I also know the full history of my 62 GPU Farm, which is running at about 0.012 BTC/day, so if that remains the same while the 72 GPU mines a higher than >0.0145 then I'll know that at this time, NiceHash is more profitable. I manage all these using Remote Desktop if on NemosMiner. Currently the 62 GPU farm is managed thru AwesomeMiner because its strictly mining X17 on AHashPool at 680MH/s Waiting for 16 more 1080ti cards to build 4 more miners 
|
|
|
FULL 12 RIG 72 GPU NICEHASH TESTOk guys, I've switched one entire farm (72 GPUs, 12 rigs) over to NiceHash (2.0.1.11) - 48 HOUR TEST!!!! https://imgur.com/a/vNodgLast 3 Payouts on AHashPool (Use to be 0.021 at its peak) 19h ago 0.01532754 330b3de0606d1257621e51301da726f8ca02... 43h ago 0.01419105 87ce1e684a440868ea347bcde8766b5ac7f8... 2d ago 0.01409336 67db48c92b113c2c98fc62461144ad8399bd... Lets see how it plays out compared to my AHashPoolPlus 62 GPU Farm
|
|
|
>>120 interval (instead of 60) where to set it?
startahashpoolplus.bat you will see a 60 value, change to 120 what to change?! script output? ADD: -interval 60
|
|
|
AHashPool beats NiceHash just by the pure fact that NiceHash most profitable algo is equihash and neoscrypt, while AHashPool has X17 and a few others that have been consistently 15-25% more profitable. Compare 24 hr actual API data from ahashpool & nicehash to see that if you calculate what your rig can do on X17 it can actually make more BTC for you over NiceHash mining equihash.
>>AHashPool beats NiceHash ^^^^^ imho it's your fanstasies, but lets test. We are talking about zpool... It's not profitable under nemosminer? I'm ready to test ahashpool. Teach me which algos to enable and which .bat use. ahashpool / ahashpool24hr / ahashpoolPlus ? Im try to 7h test NPlusMiner - аpprox $ 14.91531086 / day, disappointing result. I tried a 1.5 week long test a while back comparing nicehash vs ahash vs hash refinery. Nice hash came out on top by quite a bit. Obviously there are a lot of variables in play but it's still worth considering to do your own research. I personally just use mining calculators and evaluate if the algorithms not represented by nicehash (x17, phi, xevan, tribus) are significantly more profitable than multi-algo pools. The estimates at ahash and zpool are pretty inflated to be honest, I'd estimate they are off by 25% when calculating against the bitcoin you actually receive. I'll rerun the NH vs ahashpool (this time plus) test again after I meet my minimum on ahash. Shouldn't be using estimates... Look at 24 hour actual values instead. Hopefully you are testing with 3 identical rigs running concurrently and using ahashpoolplus with nplusminer 1.3
|
|
|
>>120 interval (instead of 60) where to set it?
startahashpoolplus.bat you will see a 60 value, change to 120
|
|
|
AHashPool beats NiceHash just by the pure fact that NiceHash most profitable algo is equihash and neoscrypt, while AHashPool has X17 and a few others that have been consistently 15-25% more profitable. Compare 24 hr actual API data from ahashpool & nicehash to see that if you calculate what your rig can do on X17 it can actually make more BTC for you over NiceHash mining equihash.
>>AHashPool beats NiceHash ^^^^^ imho it's your fanstasies, but lets test. We are talking about zpool... It's not profitable under nemosminer? I'm ready to test ahashpool. Teach me which algos to enable and which .bat use. ahashpool / ahashpool24hr / ahashpoolPlus ? Im try to 7h test NPlusMiner - аpprox $ 14.91531086 / day, disappointing result. NPlusMiner 1.3 ahashpoolplus -Algorithm xevan,tribus,c11,skein,x17,Nist5,Lyra2RE2,neoscrypt,blake2s,skunk 120 interval (instead of 60)
|
|
|
Try to use NemosMiner to maximize profit. 7*1080 noOC rig. startzpool.bat: powershell -version 5.0 -noexit -executionpolicy bypass -windowstyle maximized -command "&.\NemosMinerv2.5.ps1 -SelGPUDSTM '0 1 2 3 4 5 6' -SelGPUCC '0,1,2,3,4,5,6' -Currency USD -Passwordcurrency BTC -UIStyle Full -Wallet ***************** -Location US -ActiveMinerGainPct 3 -PoolName zpool -WorkerName ID=NemosMinerv2.5 -Type nvidia -Algorithm phi,hsr,xevan,skunk,tribus,c11,x11evo,equihash,groestl,sib,x17,blakecoin,Nist5,Lyra2RE2,neoscrypt,blake2s,lyra2z,hmq1725 Test run. Started 19:50, zpool total earned 0.00079796 BTC Check 22:10, zpool total earned 0.00091333 2.33(3) hours. Approx profit per day is $12.61  What I am doing wrong? P.S. I am hate NiceHash, but use it, because it working. NemosMiner - not. Teach me how to use it. Zpool is not going to show you accuracy for profit in 2.33 hours, you could stop mining and after 5 hours still see more profit earned In your first 2.33 hours most of that was benchmark time!!! You need to run for 48+ hours >>In your first 2.33 hours most of that was benchmark time!!! Already benchmarked, before test run. >>Zpool is not going to show you accuracy for profit in 2.33 hours, you could stop mining and after 5 hours still see more profit earned Real? Was 0.00091333, now 0.00093453 (+2.3% after stop mining this poo, approx profit $12.61->$14.95). If using of zpool api digits (insead of coins nethash/diff) don't gain profit for 2 hours - how same method will help to make profit per 48h? I don't understand. Nicehash users buy hashrate, spent it to low diff nets and gain profit. Your switching system can't beat them. They are use more advanced algorithms for switching? Pools API gives wrong digits? Im ready to long test. Other setting are right? algos, switching policy etc. AHashPool beats NiceHash just by the pure fact that NiceHash most profitable algo is equihash and neoscrypt, while AHashPool has X17 and a few others that have been consistently 15-25% more profitable. Compare 24 hr actual API data from ahashpool & nicehash to see that if you calculate what your rig can do on X17 it can actually make more BTC for you over NiceHash mining equihash.
|
|
|
Same thing here. I am running two identical rigs (8x 1070) one one NH, second one on Ahashpool with ahashpoolplus. The results after 48 hours - NiceHash 1,7 mBTC per day, ahashpool 1,4 mBTC per day.
Check your X17 hash rate make sure it hasn't gone down, I noticed mine was dropping from 80-100 down to 20-25 on most of my rigs. I had to hard set in ccminerpoly-x17 stats file and set read only attrib to prevent. My 8x1070 rigs are averaging 1.7mBTC/day on ahashpool
|
|
|
Try to use NemosMiner to maximize profit. 7*1080 noOC rig. startzpool.bat: powershell -version 5.0 -noexit -executionpolicy bypass -windowstyle maximized -command "&.\NemosMinerv2.5.ps1 -SelGPUDSTM '0 1 2 3 4 5 6' -SelGPUCC '0,1,2,3,4,5,6' -Currency USD -Passwordcurrency BTC -UIStyle Full -Wallet ***************** -Location US -ActiveMinerGainPct 3 -PoolName zpool -WorkerName ID=NemosMinerv2.5 -Type nvidia -Algorithm phi,hsr,xevan,skunk,tribus,c11,x11evo,equihash,groestl,sib,x17,blakecoin,Nist5,Lyra2RE2,neoscrypt,blake2s,lyra2z,hmq1725 Test run. Started 19:50, zpool total earned 0.00079796 BTC Check 22:10, zpool total earned 0.00091333 2.33(3) hours. Approx profit per day is $12.61  What I am doing wrong? P.S. I am hate NiceHash, but use it, because it working. NemosMiner - not. Teach me how to use it. Zpool is not going to show you accuracy for profit in 2.33 hours, you could stop mining and after 5 hours still see more profit earned In your first 2.33 hours most of that was benchmark time!!! You need to run for 48+ hours
|
|
|
|