[NemosMiner] multi algo profit switching NVIDIA/CPU miner

[millsys]

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?

Code:

"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

[camilojunior1]

plus pools are a real headache.... Just tested zergpoolplus and same issues with profits not updating.  I've switched back to the regular non 24hr version, and so far no issues updating.

[Bit2017User]

plus pools are a real headache.... Just tested zergpoolplus and same issues with profits not updating.  I've switched back to the regular non 24hr version, and so far no issues updating.

Strange i have in use both zerg and ahash plus on multiple pc and they are updating.

[Bit2017User]

Zpool and nemos, anyone is using and can tell how well is working?

[MaxiMan]

Look at this...

https://i.imgur.com/g6zNxy7.jpg

13 Hours Running 2 1080ti , one on one each pool the 24h variation
What causes this crazy peaks? I dont think its a pool issues

[k2laci]

Zergpool payout limit changed !

"BTC payouts are made automatically every 12 hours for all balances above 0.008, or 0.004 on Sunday."

Please modify earned in nemosminer.

[FalconZA]

Look at this...



13 Hours Running 2 1080ti , one on one each pool the 24h variation
What causes this crazy peaks? I dont think its a pool issues

The reflected numbers on the pools and miners are never aligned.

Some pools have connections issues which causes failed submissions, which sees rejected shares on their side. It sucks, but that's life with these pools.

[kopija]

What a day!
Been mining on Nvidias since end of 2016, and guess what: I lost my ETH virginity today.
Tired of waiting for ccminer shitcoins to wake up from winter slumber.
Before you ask: 1060s with Samsung memory, chugging ethash on MPH with 55% PL and insane memory OC.
I call that ECO-MINING

[sundownz]

Question on Zergpool -- am I correct in that it does NOT show individual worker stats ?

Thought about giving it a go... but can't deal without individual stats.

[Bit2017User]

Question on Zergpool -- am I correct in that it does NOT show individual worker stats ?

Thought about giving it a go... but can't deal without individual stats.

You have just like in ahash not on the left but on the right side

[MaxiMan]

Now that im running my both 1080TI GPU separately i noticed it records the hashrate per single GPU
But if i Run one instance for my 2 GPU it displays what is recorded for single GPU, so after the first run it updates the hashrate for the First algo it was running, then it appears to have the double from the rest profit list recorded, so it will stick to that algo

For Example: Running one 1080TI or per instance I have:
Equihash       650H/s  = 0.260 mBTC/day 
Neoscrypt  1.45MH/s  = 0.210 mBTC/day

if I set miner to run with both GPUs it starts to run the most profitable algo, but then:
Hashrate Changes:
Equihash:  650H/s  -> 1.30 KH/s = 0.520 m/BTCday ¿What happens with the rest algos?
Neoscrypt: (wont update) = 1.45MH/s = 0.300 mBTC/day (This was per single GPU)

Even when Neoscrypt per GPU is more profitable, miner wont turn to it, because Equihash shows profit for GPUs and it thinks is the double

My temporary solution for this?
I had to make 2 copies of Nemosminer folder, one for batches when i run singles GPU, and another if running all my GPUs together, so profits wont mess.

[cable_loco]

Now that im running my both 1080TI GPU separately i noticed it records the hashrate per single GPU
But if i Run one instance for my 2 GPU it displays what is recorded for single GPU, so after the first run it updates the hashrate for the First algo it was running, then it appears to have the double from the rest profit list recorded, so it will stick to that algo

For Example: Running one 1080TI or per instance I have:
Equihash       650H/s  = 0.260 mBTC/day 
Neoscrypt  1.45MH/s  = 0.210 mBTC/day

if I set miner to run with both GPUs it starts to run the most profitable algo, but then:
Hashrate Changes:
Equihash:  650H/s  -> 1.30 KH/s = 0.520 m/BTCday ¿What happens with the rest algos?
Neoscrypt: (wont update) = 1.45MH/s = 0.300 mBTC/day (This was per single GPU)

Even when Neoscrypt per GPU is more profitable, miner wont turn to it, because Equihash shows profit for GPUs and it thinks is the double

My temporary solution for this?
I had to make 2 copies of Nemosminer folder, one for batches when i run singles GPU, and another if running all my GPUs together, so profits wont mess.

For 2 gpus, you need to edit your start bat like this

-SelGPUDSTM '0 1' -SelGPUCC '0,1'

[Ragnarokt]

How to use different overclock for different miners?

[gak_45]

So who is using the 'plus' pool option? Any input on if it works better greatly appreciated. Right now Im using the ahashpool 24hour pool option. I know its more risky but it seems to work better than the 'normal' pool options. BUT if the 'plus' pool option is better would love to know!

[MaxiMan]

Now that im running my both 1080TI GPU separately i noticed it records the hashrate per single GPU
But if i Run one instance for my 2 GPU it displays what is recorded for single GPU, so after the first run it updates the hashrate for the First algo it was running, then it appears to have the double from the rest profit list recorded, so it will stick to that algo

For Example: Running one 1080TI or per instance I have:
Equihash       650H/s  = 0.260 mBTC/day  
Neoscrypt  1.45MH/s  = 0.210 mBTC/day

if I set miner to run with both GPUs it starts to run the most profitable algo, but then:
Hashrate Changes:
Equihash:  650H/s  -> 1.30 KH/s = 0.520 m/BTCday ¿What happens with the rest algos?
Neoscrypt: (wont update) = 1.45MH/s = 0.300 mBTC/day (This was per single GPU)

Even when Neoscrypt per GPU is more profitable, miner wont turn to it, because Equihash shows profit for GPUs and it thinks is the double

My temporary solution for this?
I had to make 2 copies of Nemosminer folder, one for batches when i run singles GPU, and another if running all my GPUs together, so profits wont mess.

This to keep on mind wether you change your settings OC, Number of GPUs etc... There isnt an option to make miner a bit smarter enough to know how many GPUs im using ? Since all my GPUs would be the same... there is a way to keep the hashrate per single GPU (with same OC settings) and then just multiply by number of active GPU at that time?
Looks like it will need a Benchmark everytime I add or change something on my system (GPUs, OC)

[sundownz]

Is it normal for Version 2.5.1 to display some negative projected earnings using Ahashpoolplus ?

I am going back and forth about what pool / method to switch to... benching a few system with Ahashpoolplus / NEMO 2.5.1 and noticed this.

[fireanimal]

Happened to me earlier today as well on AHASHPOOL PLUS.  Seems to have corrected itself now, maybe had to do with the market drop.

[MrPlus]

So who is using the 'plus' pool option? Any input on if it works better greatly appreciated. Right now Im using the ahashpool 24hour pool option. I know its more risky but it seems to work better than the 'normal' pool options. BUT if the 'plus' pool option is better would love to know!

Plus makes more than 24hr generaly
Have a look there: https://github.com/MrPlusGH/NPlusMiner/releases
Give it a go and let us know.

[MrPlus]

Happened to me earlier today as well on AHASHPOOL PLUS.  Seems to have corrected itself now, maybe had to do with the market drop.

This sometimes happens on Plus when huge drop occurs.
This is in line with the Plus logic and keeps us away from algos dropping too much

[MrPlus]

Now that im running my both 1080TI GPU separately i noticed it records the hashrate per single GPU
But if i Run one instance for my 2 GPU it displays what is recorded for single GPU, so after the first run it updates the hashrate for the First algo it was running, then it appears to have the double from the rest profit list recorded, so it will stick to that algo

For Example: Running one 1080TI or per instance I have:
Equihash       650H/s  = 0.260 mBTC/day 
Neoscrypt  1.45MH/s  = 0.210 mBTC/day

if I set miner to run with both GPUs it starts to run the most profitable algo, but then:
Hashrate Changes:
Equihash:  650H/s  -> 1.30 KH/s = 0.520 m/BTCday ¿What happens with the rest algos?
Neoscrypt: (wont update) = 1.45MH/s = 0.300 mBTC/day (This was per single GPU)

Even when Neoscrypt per GPU is more profitable, miner wont turn to it, because Equihash shows profit for GPUs and it thinks is the double

My temporary solution for this?
I had to make 2 copies of Nemosminer folder, one for batches when i run singles GPU, and another if running all my GPUs together, so profits wont mess.

For 2 gpus, you need to edit your start bat like this

-SelGPUDSTM '0 1' -SelGPUCC '0,1'

Have a look here: https://github.com/MrPlusGH/NPlusMiner/releases
Might be easier to set up.