Topic: [NemosMiner] multi algo profit switching NVIDIA/CPU miner - page 33. (Read 289464 times)

Hey,

Could anyone clarify how monitor script works? If I open it, it monitors my cards, everything is great, but after some time it just disappears.

Thanks

https://github.com/nemosminer/NemosMiner/issues/375

Best Regards
Nemo

It is possible to add new miners, it's just a bit tricky the first time around.

If you go to the Miners folder you'll see all the currents miners listed, to add RavenEnemy which I think it's ccminer, I'd copy and rename an existing ccminer*.ps1 file, then edit the files to do the necessary changes to make it run your new miner.  In the case of Excavator it's a lot trickier, I'd recommend copy the excavatorNvidianeo.ps1 from SniffDogMiner and edit it to make the changes you need.

Quick question, where do you download RavenEnemy from? 

The problem with keeping everything in a single folder is that the hashrates will get all out of wack.  Say for example, copyA is mining C11, copyB is mining X17.  CopyA has been running for 60 seconds now it's going to update the saved C11 hashrate to the current value, to do so is going to see what ccminer is reporting on port 4068, but since copyB is also running ccminer on port 4068, then copyA will save X17's hashrate as the benchmarked hashrate for C11 and throw the whole switching algo out of whack.

You can avoid this by making the saved hashrates read-only after the initial benchmarking, but you don't get the live hashrate updates, which it's not a biggie, I just like the otherway better 

How do I specify to use different miners? Neoscrypt for example defaults to KlausT, but Excavator gives 30% better performance. Same with RavenEnemy vs Raven225 build here

I did not make a new folder. Just make a copy of startpool.bat and change dstm settings as 0 1 2 3 4 to 5 6 7 8 etc.

Have you tried running 2 instances of the miner? You make 1 copies of the mine and run 6 cards on it (0,1,2,3,4,5), then you make a 2nd copy, on this one go to the Miners folder and change the port (-b) on all the miners you'll be using (e.g. ccminer default port is 4068, change it to 4069), then run the remaining 6 cards (6,7,8,9,10,11).

NPlusMiner does the miner port change for you, I just don't know whats others differences there are between Nemos and NPM.

Sorry to say man, but your assertion is completely wrong.  The issue is not the miner since your hashrates have remained pretty much the same, the problem is the pay rates from the pool (the BTC/GH/day column).  For example X17 dropped from 0.02381 to 0.01680, that's huge, and those values depend on the pool you choose, not the miner.

And as a side note, you shouldn't pay too much attention to the USD/day column since the price of BTC is such a roller-coaster, instead always look at the mBTC/day column instead.  This value should remain constant for the most part but every 2-3 months you'll see a big reduction due to mining difficulty always increasing.

how do you fix the problems with CCminer... most of the ccminer from polytimus and alexis have problem running 12 cards..

always giving non existent cuda device error , tpruvot doesn't have this problem

hi dud i install this app now and test it  is it good ? 
 and about your pic !! check your benchmark man         u have Diff bench !! in 2 pic

Comparison of version 2.5.2 to version 3.0
version 2.5.2 is much better than 3.0, almost 40% greater than 2.5.2 something is wrong in version 3.0, compare the images

Version 3.0
https://prnt.sc/isle0n

Version 2.5.2
https://prnt.sc/isle4t

You could setup if you switch to manual edition of the config files.
However, NPlusMiner now supports running multiple instances. I guess that might ease your life
https://github.com/MrPlusGH/NPlusMiner/releases

I've been testing the version 3 yesterday and I have an issue to report. It might be something I overlooked because of the new design, but let me start by explaining how I work the version 2 atm.

I have 2 different kinds of cards on my rig, so each kind of card is more profitable in different algos. Because of that, I don't want to run an average of all my cards on every algo and instead I've made 2 folders of NemosMiner, each folder with different data inside the "stats" folder and I run 2 instances at the same time, one for each group of cards.
At first the benchmark would get confused when two ccminers were running and it'd update the hashrate incorrectly. In order to fix that, I run the benchmark on the 1st group and then turned the "*HashRate.txt" files into read-only. I then benchmarked the 2nd group of cards and again locked their hashrate files into read-only. Since then, running 2 instances at the same time works like charm, the only drawback is that the hashrates are not being updated automatically but if you don't change anything in your system, the hashrate rarely changes because of an updated miner... and of course you can just run the benchmark again!

I believe the above trick would help people with more cards than the miner can handle? Maybe?

Anyway to be honest I posted the above long explanation in case someone wants to try it, the issue I have with version 3 with the above setup is pretty simple... I can't setup specific cards for each instance OR I'm doing it wrong and there's no documentary to help me!

hi manc

the port is correct we use : AUTO SWITCHING PORTS PER ALGO. SORTED FOR NVIDIA GPU

Algo   Current Coin   Port   Norm. Profit   Total Hash   Coins
Equihash   Zencash   17023   0.21373   85.12M   4
Lyra2RE2   Monacoin   17018   0.20423   1.11T   2
Lyra2z   Zcoin   17025   0.19773   129.40G   1
Ethash   Ethereum   17020   0.19016   28.08T   4

you are referring to :  COIN MINING STATUS AND PROFITS. SORTED FOR NVIDIA GPU

Coin   Algo   Port   Norm. Profit   Pool Hash   Last Block
Zencash   Equihash   20594   0.21373   3.03M   20m ago
Monacoin   Lyra2RE2   20593   0.20423   1.04T   36s ago
Zcash   Equihash   20570   0.20103   39.74M   22m ago
Zcoin   Lyra2z   20581   0.19773   129.40G   16m ago
Ethereum   Ethash   20535   0.19016   27.32T   1m ago

Regards
Nemo

thanks "primo1983"
im in the process of reviewing all ccminers atm so will be changes made before v3.0 is released to rectify that problem with 12GPUS

Regards
Nemo

hmm... Looks like a miner issue. ccminer alexis is seeing only 8.
May be some info here (even if for more GPUS): https://github.com/nemosminer/NemosMiner/issues/133

Let people know your findings.

9 - GTX 1080 TI

Says 8 threads.
Do you have 9 or 8 Cards?

C:\Users\Rig1\Desktop\NemosMiner-master\Bin>NVIDIA-TPruvotcuda9\ccminer.exe -b 4068 -a tribus -o stratum+tcp://tribus.mine.ahashpool.com:8533 -u 1FJ67bzAa4V3Sf8S7EH41NRTdB -p ID=NPlusMiner13,c=BTC --api-remote --api-allow=0/0
*** ccminer 2.2.4 for nVidia GPUs by tpruvot@github ***
    Built with VC++ 2013 and nVidia CUDA SDK 9.0 32-bits

  Originally based on Christian Buchner and Christian H. project
  Include some kernels from alexis78, djm34, djEzo, tsiv and krnlx.

BTC donation address: 1AJdfCpLWPNoAMDfssVgKSSTHxPo (tpruvot)

[2018-03-17 15:27:32] Starting on stratum+tcp://tribus.mine.ahashpool.com:8533
[2018-03-17 15:27:32] NVAPI GPU monitoring enabled.
[2018-03-17 15:27:32] 8 miner threads started, using 'tribus' algorithm.
[2018-03-17 15:27:33] API open in full access mode to 0/0 on port 4068
[2018-03-17 15:27:34] Stratum difficulty set to 0.8
[2018-03-17 15:27:34] tribus block 643056, diff 4808.912
[2018-03-17 15:27:34] GPU #0: Intensity set to 20, 1048576 cuda threads

Sorry, you need to remove the " -d" as well