[NemosMiner] multi algo profit switching NVIDIA/CPU miner

[brenosabino]

sorry guys but im a noob on multi algo. is it worth it using on a 970? how does it know which one is most profit? it should be running equihash but starts on ethash (mph). can i run a benchmark and manually input values?

[newmz]

i keep checking back to see if this is ready yet.... later today you said. It's getting pretty late.

c'mon release it already!

[Storx]

Is there some way to benchmark the algos easier, seen .txt file above that had specific numbers listed as benchmarks for each algo.. how did yall do that? im linking what im talking about

Code:

[2017-06-08 15:44:54]    blakecoin :    8304139.4 kH/s, -10999 MB, 67108864 thr.
[2017-06-08 15:44:54]        blake :    4767552.0 kH/s,     2 MB, 67108864 thr.
[2017-06-08 15:44:54]      blake2s :    6717441.6 kH/s,     2 MB, 33554432 thr.
[2017-06-08 15:44:54]          bmw :    2876996.4 kH/s,    66 MB,  2097152 thr.
[2017-06-08 15:44:54]      bastion :      19386.4 kH/s,   234 MB,  1048576 thr.
[2017-06-08 15:44:54]         deep :      66240.6 kH/s,    34 MB,   524288 thr.
[2017-06-08 15:44:54]       decred :    4961711.2 kH/s,     2 MB, 33554432 thr.
[2017-06-08 15:44:54]        fresh :      25065.3 kH/s,   610 MB,   524288 thr.
[2017-06-08 15:44:54]     fugue256 :     723228.2 kH/s,   130 MB,  4194304 thr.
[2017-06-08 15:44:54]      groestl :      68094.8 kH/s,     2 MB,   524288 thr.
[2017-06-08 15:44:54]        heavy :      64930.8 kH/s,   166 MB,   524032 thr.
[2017-06-08 15:44:54]      hmq1725 :       7810.9 kH/s,   644 MB,   524288 thr.
[2017-06-08 15:44:54]       keccak :    1026037.0 kH/s,   130 MB,  2097152 thr.
[2017-06-08 15:44:54]      jackpot :      18548.2 kH/s,   108 MB,  1048576 thr.
[2017-06-08 15:44:54]          jha :      25728.4 kH/s,   134 MB,  1048576 thr.
[2017-06-08 15:44:54]         lbry :     492183.5 kH/s,     2 MB,  8388608 thr.
[2017-06-08 15:44:54]        luffa :     549619.1 kH/s,   130 MB,  2097152 thr.
[2017-06-08 15:44:54]        lyra2 :       5103.1 kH/s,    12 MB,    65536 thr.
[2017-06-08 15:44:54]      lyra2v2 :      64216.9 kH/s,  1570 MB,  1048576 thr.
[2017-06-08 15:44:54]       lyra2z :       2651.5 kH/s,    12 MB,    65536 thr.
[2017-06-08 15:44:54]       myr-gr :     124930.4 kH/s,    66 MB,  1048576 thr.
[2017-06-08 15:44:54]    neoscrypt :       1475.3 kH/s,   306 MB,    65536 thr.
[2017-06-08 15:44:54]        nist5 :      83465.4 kH/s,    66 MB,  1048576 thr.
[2017-06-08 15:44:54]        penta :      26863.5 kH/s,    34 MB,   524288 thr.
[2017-06-08 15:44:54]        qubit :      32965.1 kH/s,   610 MB,   524288 thr.
[2017-06-08 15:44:54]      sha256d :    1846864.9 kH/s,     2 MB, 33554432 thr.
[2017-06-08 15:44:54]      sha256t :    1066858.2 kH/s,     2 MB,  8388608 thr.
[2017-06-08 15:44:54]          sia :    3129930.5 kH/s,     2 MB, 67108864 thr.
[2017-06-08 15:44:54]          sib :      15462.1 kH/s,  1218 MB,  1048576 thr.
[2017-06-08 15:44:54]        skein :     706579.5 kH/s,     2 MB,  1048576 thr.
[2017-06-08 15:44:54]       skein2 :     640114.9 kH/s,    34 MB,   524288 thr.
[2017-06-08 15:44:54]           s3 :      66537.9 kH/s,   610 MB,   524288 thr.
[2017-06-08 15:44:54]   timetravel :      21979.2 kH/s,    34 MB,   524288 thr.
[2017-06-08 15:44:54]      bitcore :      27810.0 kH/s,   610 MB,   524288 thr.
[2017-06-08 15:44:54]       x11evo :      12635.2 kH/s,   610 MB,   524288 thr.
[2017-06-08 15:44:54]          x11 :      16460.0 kH/s,   610 MB,   524288 thr.
[2017-06-08 15:44:54]          x13 :      17518.1 kH/s,   610 MB,   524288 thr.
[2017-06-08 15:44:54]          x14 :      17889.2 kH/s,   610 MB,   524288 thr.
[2017-06-08 15:44:54]          x15 :      17076.3 kH/s,   610 MB,   524288 thr.
[2017-06-08 15:44:54]          x17 :      16736.9 kH/s,   610 MB,   524288 thr.
[2017-06-08 15:44:54]      vanilla :    6290462.1 kH/s,     2 MB, 16777216 thr.
[2017-06-08 15:44:54]       veltor :      39056.8 kH/s,   130 MB,  2097152 thr.
[2017-06-08 15:44:54]    whirlpool :      78090.1 kH/s,     2 MB,   524288 thr.
[2017-06-08 15:44:54]          zr5 :       6622.8 kH/s,    88 MB,   262144 thr.
[2017-06-08 15:44:54] GPU #1: Intensity set to 18, 262144 cuda threads

I don't know about all versions, but the tpruvot fork you can run with `--benchmark`

So do you just create a batch with that command?

[yslyung]

i keep checking back to see if this is ready yet.... later today you said. It's getting pretty late.

c'mon release it already!

OP is doing it for FREE !

so just wait & be patient & be polite.

[zer0k]

i keep checking back to see if this is ready yet.... later today you said. It's getting pretty late.

c'mon release it already!

OP is doing it for FREE !

so just wait & be patient & be polite.

Or make a demand with a BTC donation

[CiscoStud]

i keep checking back to see if this is ready yet.... later today you said. It's getting pretty late.

c'mon release it already!

yeh i am a human with a real job and  i also need sleep...

so how about NO

Nemo

I just started mining again and I won't forget about you when I cash out every month!

I'll be sure to always donate!



Cheers!

[^BuTcH^]

Is NemosMiner more profitable than nicehash?
How much can I earn daily with two 1070?

[DaniRC]

Is NemosMiner more profitable than nicehash?
How much can I earn daily with two 1070?

Same question for 2 1080 ti. I would like to chek if my stats are correct..

[kopija]

testing atm will be uploaded 2moro sorry for delay

No need to feel sorry. Feel proud.
You are one of the heroes of cryptomining world, after all.

[Storx]

Could someone explain to me the difference between intensity and difficulty levels in the miners? I ask because i am trying to dial in my GPU's for the most profit/watt and when i was running skein 24/7 2 weeks ago i managed to dial it in at 6.2Mh/s per watt compared to 2.1Mh/s on OEM settings.. so literally 3x's the efficiency fine tuning it.. but after reading more into nemo's multi-algo when skein took a huge drop in profit last week and i very quickly found that the gpu settings for my stable skein mining was like 80% chance of crashing on other coins, so i have been fighting with them to fine a happy medium as i introduce more coins to the list to mine.. im out to 5 so far stable but i feel like this should be easier... for example i have lyra2v2 set to the lowest intensity setting 8 for ccmineralexa78 and if the difficulty number doesnt climb as high during mining the coin will mine all day 24/7, but when it jumps pass a certain point in difficulty the miner just goes into a GPU Miner error state and crashes...

So i am trying to understand more about the intensity vs difficulty levels as im a new miner still learning...

A tip for the multi-gpu miners, i found that running separate batch files for each card is WAY more stable that trying to group the settings together.. for example my center GPU's in my rig are able to mine skein at intensity of 27 only, but my outer colder ones can do as high as 30 intensity without ever crashing... so right now my setup is at its most stable condition running multiple Nemo-Miners in the background all running separate GPU's on different settings...  it does confuse me when some will mine 1 coin and others mine another coin at the same exact moment... not exactly sure how the whole grabbing which one is most profitable thing works when im literally using the same computer mining these different batch files...

[a4si]

Is there any way that one could set up how often does the miner do the switching - for example only 1 per hour? Or is this decided by the pool itself?

Namely, I've notice that some times it switches ever 5-10min (I've mining only 2 different algos) and given the fact that not all cards rump up immediately the rig is working let say with only half of hashing power. And after several minutes when all cards are up to speed the miners already switches to new algo... effectively this means that rig is hashing not with full but lets say half or 2/3 of power. Wondering if this is still more profitable vs possibility to set up switch to happen let's say max 1 per hour?

thx

[minerx117]

NemosMiner-v1.7.5-ZPOOL

update to EWBF +2%speed (equihash)
added separate .bat file for 1050ti,1060,1070,1080ti more accurate speeds..
add sp-mod to the miners so users have the option instead of alexis78..
add Device Command to select certain gpus
added custom -i intensities for each card (1050ti,1060,1070,1080ti)  


NemosMiner-v1.7.2-MPH

update to EWBF +2%speed (equihash)
add sp-mod to the miners so users have the option instead of alexis78..
update to ccminercryptonight

[miliard]

NemosMiner-v1.7.5-ZPOOL

update to EWBF +2%speed (equihash)
added separate .bat file for 1050ti,1060,1070,1080ti more accurate speeds..
add sp-mod to the miners so users have the option instead of alexis78..
add Device Command to select certain gpus
added custom -i intensities for each card (1050ti,1060,1070,1080ti)  


NemosMiner-v1.7.2-MPH

update to EWBF +2%speed (equihash)
add sp-mod to the miners so users have the option instead of alexis78..
update to ccminercryptonight

Great! Thanks a lot mate.

[sypher9]

Huge thanks for this ! I've been wishing to see the ability to select GPU's and am really excited to see you've added this to the Zpool version!!!

In that spirit, I attempted to update your MPH code to include the GPU selection you added to the Zpool code.

This is what I came up with, let me know if I messed up anywhere:
NemosMiner-v1.7.2-MPH_GPU_SELECT.bat

Code:

@echo off
SETLOCAL EnableExtensions
SET USER=nemo.1050ti
SET PASS=x
SET GPUequihash=0
SET GPUccminer=0
SET A=ethminer.exe
SET B=zminer.exe
SET C=ccminersp-mod
SET D=ccminerAlexis78.exe
SET E=ccminerTanguy.exe
SET POOL=hub.miningpoolhub.com
:start
ECHO Starting NemosMiner-v1.7.2 if this helped you please donate #Nemo.... 
%A% --cuda-devices %GPUequihash% --farm-retries 0 -U -S us-east.ethash-%POOL%:12020 -O %USER%:%PASS% -FS exit
%B% --cuda-devices %GPUequihash% --server us-east.equihash-%POOL% --port 12023 --fee 0 --eexit 2 --user %USER% --pass %PASS%
%E% -d %GPUccminer% -r 0 -a cryptonight -o stratum+tcp://us-east.cryptonight-%POOL%:12024 -u %USER% -p %PASS%
%D% -d %GPUccminer% -r 0 -a neoscrypt -o stratum+tcp://%POOL%:12012 -u %USER% -p %PASS% -i 15
%E% -d %GPUccminer% -r 0 -a groestl -o stratum+tcp://%POOL%:12004 -u %USER% -p %PASS%
%D% -d %GPUccminer% -r 0 -a lyra2v2 -o stratum+tcp://%POOL%:12018 -u %USER% -p %PASS%
%D% -d %GPUccminer% -r 0 -a myr-gr -o stratum+tcp://%POOL%:12005 -u %USER% -p %PASS%
%D% -d %GPUccminer% -r 0 -a skein -o stratum+tcp://%POOL%:12016 -u %USER% -p %PASS%
ECHO Starting NemosMiner-v1.7.2 if this helped you please donate #Nemo....
GOTO start

Edit: also switched to us-east servers, because I'm not in Asia
Edit2: changed "cuda_devices" for "cuda-devices"
Edit3: changed "-G" for "-U"

[creat326]

Hi there,
I've just tried the new NemosMiner-v1.7.2-MPH and it crashes on my 1080ti
It begins running fine, then the screen goes black and when it recovers it's gone. I've tried several times with no luck. Here the log on the screen:

+-------------------------------------------------+
|         EWBF's Zcash CUDA miner. 0.3.4b         |
+-------------------------------------------------+
INFO: Current pool: asia.equihash-hub.miningpoolhub.com:12023
INFO: Selected pools: 1
INFO: Solver: Auto.
INFO: Devices: All.
INFO: Temperature limit: 90
INFO: Api: Disabled
---------------------------------------------------
INFO: Target: 0002641df360a267...
CUDA: Device: 0 GeForce GTX 1080 Ti, 11264 MB i:64
INFO: Detected new work: 8b8
CUDA: Device: 0 Selected solver: 0
INFO: Detected new work: 8b9
Temp: GPU0: 62C
GPU0: 707 Sol/s
Total speed: 707 Sol/s
CUDA: Device: 0 Thread exited with code: 4
Temp: GPU0: 0C
GPU0: 694 Sol/s
Total speed: 694 Sol/s
INFO: Target: 00036a73edf7c36e...
INFO: Detected new work: 8ba
Temp: GPU0: 0C
GPU0: 0 Sol/s
Total speed: 0 Sol/s
Temp: GPU0: 0C
GPU0: 0 Sol/s
Total speed: 0 Sol/s
ERROR: Looks like GPU0 are stopped. Restart attempt.

[sypher9]

Not sure what to say except that it works fine on my 1080Ti using NemosMiner-v1.7.2-MPH.

I'm guessing you already tried restarting your computer, resetting the overclock, checking the timezone, checking the server is the closest to you, etc.?

[creat326]

Yeah I already tried reset, no OC, clean... as soon as it begins running EWBF it goes dead. Any other seems to work fine.

[newmz]

So I have a rig which is 2 x1070s and 2 x 1060s

would it be feasible to run the 1070.bat and just enumerate the 1070s then run the 1060.bat on THE SAME RIG and just enumerate the 1060s?
Or will this mean that some algos will be trying to mine with all GPUs twice? Like when it's using "zminer"?

Maybe I wil be better off just using the MPH miner?

[sypher9]

I started running two .bat files on the same rig this morning. So far it seems to be working fine.

I have a Zpool.bat file running on my 1st 1080 Ti and a MPH.bat file running on my 2nd 1080 Ti.

I'm trying this out so that I can compare the returns between Zpool and MPH. I'll report the results in a day or two.

[JaredKaragen]

Could someone explain to me the difference between intensity and difficulty levels in the miners? I ask because i am trying to dial in my GPU's for the most profit/watt and when i was running skein 24/7 2 weeks ago i managed to dial it in at 6.2Mh/s per watt compared to 2.1Mh/s on OEM settings.. so literally 3x's the efficiency fine tuning it.. but after reading more into nemo's multi-algo when skein took a huge drop in profit last week and i very quickly found that the gpu settings for my stable skein mining was like 80% chance of crashing on other coins, so i have been fighting with them to fine a happy medium as i introduce more coins to the list to mine.. im out to 5 so far stable but i feel like this should be easier... for example i have lyra2v2 set to the lowest intensity setting 8 for ccmineralexa78 and if the difficulty number doesnt climb as high during mining the coin will mine all day 24/7, but when it jumps pass a certain point in difficulty the miner just goes into a GPU Miner error state and crashes...

So i am trying to understand more about the intensity vs difficulty levels as im a new miner still learning...

A tip for the multi-gpu miners, i found that running separate batch files for each card is WAY more stable that trying to group the settings together.. for example my center GPU's in my rig are able to mine skein at intensity of 27 only, but my outer colder ones can do as high as 30 intensity without ever crashing... so right now my setup is at its most stable condition running multiple Nemo-Miners in the background all running separate GPU's on different settings...  it does confuse me when some will mine 1 coin and others mine another coin at the same exact moment... not exactly sure how the whole grabbing which one is most profitable thing works when im literally using the same computer mining these different batch files...

This gives me an idea to expand and have it apply nvidia profiles per algo....  This is an interesting task.   would take a bit of end-user work to trim for their own systems when it comes down to it... but I believe I can add the functionality to change your OC settings automatically with the algo change.  And I think I can do it dynamically based on what algo is mining....  (I think I can see the code in my head at this point)

"intensity vs. difficulty" is surely not a thing.   intensity is how many concurrent hashing threads your GPU is running;  difficulty is the value of the result the GPU provides.....