[NemosMiner] multi algo profit switching NVIDIA/CPU miner

[tio]

Hi all.
What is timing interval did you setup on the pool auto switch? i realize that 300 seconds sometimes its not enough to finish the job


Last Refresh: 02/11/2018 14:31:20
Sleep 300 sec
--------------------------------------------------------------------------------
Running:

[jimmykl]

If you remove timetravel and restart, it should skip the ones already benchmarked.

Thanks for the reply. I already stopped the benchmarking and switched the card over to mining Verge for a day or two while I sort out what went wrong. Based on the copy-n-paste of the miner window output above it looks like the connection wasn't set up properly (ie - the stratum and port). Unfortunately, I didn't check the miner window at any other time so can't say if this is anomalous or not...

Don't even worry about troubleshooting timetravel. If the algo isn't included in your .bat file nemos won't benchmark it.

As nemos benchmarks each algo (which takes up to 6 minutes per algo *never* hours) it creates a file in the Stats folder e.g. ccminerpolytimos_ALGO_HashRate.txt If a file exists it won't benchmark that algo. So if you want to rerun a particular benchmark you can delete the relevant file and it won't have to run them all.

[cryptomoblo]

Since thursday evening I started concurrent test between ahashpool and blazepool with 3x GTX 1080 ti.

Currently blazepool is a head by a small margin:

Ahashpool: 0.00421241
Blazepool: 0.00444645

Zergpool is also up again and will continue testing it coming week.

[tio]

Since thursday evening I started concurrent test between ahashpool and blazepool with 3x GTX 1080 ti.

Currently blazepool is a head by a small margin:

Ahashpool: 0.00421241
Blazepool: 0.00444645

Zergpool is also up again and will continue testing it coming week.

Is that a daily’s income? Or total income since Thursday?!

[kollom]

some problems with veltor algo on zpool, not pass the benchmark (no connection). nemos 2.4.1

[tio]

some problems with veltor algo on zpool, not pass the benchmark (no connection). nemos 2.4.1

Just comment this line into the miner to skip this test, these same problem with memos 2.4.2.
Helped to me

[yashart]

anyone else having issues with neoscrypt today? Every time the miner switches to this algo, the miner windows just crashes/disappears. Never saw this prior to this morning...

i had few hours ago, just re run benchmark making sure PalginNeoHasrate.txt is blank

Still no luck. Doesn't make sense to me, this was working perfectly up until a day ago. I am still running nemos 2.3.... Decided to try moving to 2.4.2, but ccminer crashed on at least half of the benchmarks like others have reported.

For a sanity check, I went back and re-benchmarked all algo's on 2.3. Everything works with the exception of neoscrypt.

No windows updates. No driver updates. No system changes at all.

[MagicSmoker]

If you remove timetravel and restart, it should skip the ones already benchmarked.

Thanks for the reply. I already stopped the benchmarking and switched the card over to mining Verge for a day or two while I sort out what went wrong. Based on the copy-n-paste of the miner window output above it looks like the connection wasn't set up properly (ie - the stratum and port). Unfortunately, I didn't check the miner window at any other time so can't say if this is anomalous or not...

Don't even worry about troubleshooting timetravel. If the algo isn't included in your .bat file nemos won't benchmark it.

As nemos benchmarks each algo (which takes up to 6 minutes per algo *never* hours) it creates a file in the Stats folder e.g. ccminerpolytimos_ALGO_HashRate.txt If a file exists it won't benchmark that algo. So if you want to rerun a particular benchmark you can delete the relevant file and it won't have to run them all.

And thank you for the reply as well. I'm not at all worried about missing out on the one and only coin I could find that uses the timetravel algo (machinecoin), but I am concerned that a connection issue doesn't get noticed by the script, at least during benchmarking. I also suspect that this affects the original NemosMiner, and not just the MrPlus fork, so still relevant to this thread.

[tio]

Guys, do you know if the algorithm will be switched over after the mining  block finished?! Or it will be switched as the sleep time setup?

[baenregod]

Testing ahashpool vs blazepool, current profit .bats (not 24hr actual) with a 5% switch and 30s interval, each with a 6 x 1070 rig, they are overclocked the same, 75%/100/500, but have slightly different hash rates due to different models in each, but fairly close. I had to disable keccak on blazepool bc it kept showing the profit as orders of magnitude off.

Currently about a day into the test, the btc/24hr is approximately the following:
blazepool - 0.0018384
ahashpool - 0.0015329

So currently blazepool is winning by about 20% 1 day in. I'll try to keep going for at least a few days. Hopefully the rigs stay online the same, I've had occasional trouble with them hanging up every once in a while, can't figure out why, which would skew the results.

Approximately 48 hours into the test, the btc/24hr is approximately the following:
blazepool - 0.002033
ahashpool - 0.001481

My ahash rig did appear to go for part of the night while I slept, which I tried to account for in the above calculations. There's a chance it has gone down other times as well that I haven't seen (I have it restart the whole rig every 12 hours), but I believe this is fairly accurate. Blazepool appears to be pulling ahead, now approximately 37% more profitable. Even if I add in a bunch more hours of downtime into the calcs, blazepool is still ahead; they may have gotten lucky with blocks recently though. I'll keep it going for a while more, hopefully my rigs cooperate and don't go down anymore.

[tio]

How did You solved the problem with GPU driver crashing when NemosMiner shuts down miner app?
Is the solution maybe to make one dummy Afterburner profile (e.g profile5) that is CoreClock 0, MemoryClock -502, PowerLimit 70 and to load that profile 30 seconds before miner shuts down?
I don't know... All these miner/algo/pool changing apps are cool (Nemosminer, Megaminer, AwesomeMiner) but they are absolutely useless for me if the driver crashes and the rig is not mining until manual restart.
Rig restart function would be also good for this problem. (e.g I have 4 cards in rig, mining app detects only 3 then reboot).

Thank's and excuse me if there was any discussion on this topic.

Nothing to solve, the software does not crash when nemos switches miner. You are stating it happens with other software too. Did you look in other direction like overclocking, faulty riser(s) or issue with motherboard, fresh install of windows etc.

BRAVO minerx117 !!!
In NemosMiner v.2.4.2 there is monitor\Monitor_Xcard.bat script and it restarts computer if driver hangs. Jeeee.... testing...
The other nince candy is in prerun folder! The NemosMiner can overclock gpu using nvidiaInspector app for every algorithm. ....working like a charm...

Thanks!

Hi Miodragk,
did you already use nvidiaInspector with v 2.4.2? where you put the .exe file?

thanks

[cryptomoblo]

Since thursday evening I started concurrent test between ahashpool and blazepool with 3x GTX 1080 ti.

Currently blazepool is a head by a small margin:

Ahashpool: 0.00421241
Blazepool: 0.00444645

Zergpool is also up again and will continue testing it coming week.

Is that a daily’s income? Or total income since Thursday?!

Its income since Thursday:

Current profit, blazepool margin is increasing:

Ahashpool: 0.00478314
Blazepool: 0.00553579

Just had payout from ahashpool. Might switch the other 3 gpus to blazepool as wel or start testing again with zergpool.

EDIT: I found that on ahashpool it was stuck on mining x17 algo, so it probably was not mining most profitable for atleast 6 hours. Somehow my hashrate got messed up. Probably reason for the bigger difference in profit between ahashpool and blazepool.

[HanopkaH]

Since thursday evening I started concurrent test between ahashpool and blazepool with 3x GTX 1080 ti.

Currently blazepool is a head by a small margin:

Ahashpool: 0.00421241
Blazepool: 0.00444645

Zergpool is also up again and will continue testing it coming week.

Is that a daily’s income? Or total income since Thursday?!

Its income since Thursday:

Current profit, blazepool margin is increasing:

Ahashpool: 0.00478314
Blazepool: 0.00553579

Just had payout from ahashpool. Might switch the other 3 gpus to blazepool as wel or start testing again with zergpool.

EDIT: I found that on ahashpool it was stuck on mining x17 algo, so it probably was not mining most profitable for atleast 6 hours. Somehow my hashrate got messed up. Probably reason for the bigger difference in profit between ahashpool and blazepool.

I got 2 rigs with 5 1060 each with a lil difference in hash rates and im gonna try your test also to see which is more profitable.

Benchmarking now and will report tommorow at 12:00 if i dont forget

[cryptomoblo]

Since thursday evening I started concurrent test between ahashpool and blazepool with 3x GTX 1080 ti.

Currently blazepool is a head by a small margin:

Ahashpool: 0.00421241
Blazepool: 0.00444645

Zergpool is also up again and will continue testing it coming week.

Is that a daily’s income? Or total income since Thursday?!

Its income since Thursday:

Current profit, blazepool margin is increasing:

Ahashpool: 0.00478314
Blazepool: 0.00553579

Just had payout from ahashpool. Might switch the other 3 gpus to blazepool as wel or start testing again with zergpool.

EDIT: I found that on ahashpool it was stuck on mining x17 algo, so it probably was not mining most profitable for atleast 6 hours. Somehow my hashrate got messed up. Probably reason for the bigger difference in profit between ahashpool and blazepool.

I got 2 rigs with 5 1060 each with a lil difference in hash rates and im gonna try your test also to see which is more profitable.

Benchmarking now and will report tommorow at 12:00 if i dont forget

Nice! looking forward to your results

[jdubya]

I have a rig with 11 cards.  If I list card -d 10, CCMiner recognizes the card as card 0 and ignores the 1 in 10.  So when I am benchmarking, CCMiner uses card 0 twice causing many algos to crash CCminer.  I tried removing the -d list of cards in the startpool.bat file, but then it defaults to 2 cards for benchmarking and mining.  What file can I change to remove the -d card list so the miners just default to all cards?

Any help would be appreciated.  Thanks in advance.

[millsys]

I have a rig with 11 cards.  If I list card -d 10, CCMiner recognizes the card as card 0 and ignores the 1 in 10.  So when I am benchmarking, CCMiner uses card 0 twice causing many algos to crash CCminer.  I tried removing the -d list of cards in the startpool.bat file, but then it defaults to 2 cards for benchmarking and mining.  What file can I change to remove the -d card list so the miners just default to all cards?

Any help would be appreciated.  Thanks in advance.

Some of the miners don't support card #11 (10) and think its card #1 (0)
Run NemosMiner on first 8 cards is best (0-7) then have separate batch running against blaze2s, phi, or x17 continuously for other cards using TPruvotcuda9/ccminer 2.2.4 which DOES support -d 8,9,10,11

[jdubya]

I have a rig with 11 cards.  If I list card -d 10, CCMiner recognizes the card as card 0 and ignores the 1 in 10.  So when I am benchmarking, CCMiner uses card 0 twice causing many algos to crash CCminer.  I tried removing the -d list of cards in the startpool.bat file, but then it defaults to 2 cards for benchmarking and mining.  What file can I change to remove the -d card list so the miners just default to all cards?

Any help would be appreciated.  Thanks in advance.

Some of the miners don't support card #11 (10) and think its card #1 (0)
Run NemosMiner on first 8 cards is best (0-7) then have separate batch running against blaze2s, phi, or x17 continuously for other cards using TPruvotcuda9/ccminer 2.2.4 which DOES support -d 8,9,10,11

Thanks!
If I did that would have to have 2 instances of Nemos running?

[Dragstar]

question to nvidia users should i mine only neoscrypt algo with 1060-1070 cards or all algos that pool supports?

[jimmykl]

question to nvidia users should i mine only neoscrypt algo with 1060-1070 cards or all algos that pool supports?

not much point using a multiminer with just one algo!

right now my 1060s top 5: tribus, neoscrypt, x17, phi, lyra2re2

and 1070s: skein, phi, x17, bitcore, lyra2re2

(obv pool dependent and subject to change)

[millsys]

I have a rig with 11 cards.  If I list card -d 10, CCMiner recognizes the card as card 0 and ignores the 1 in 10.  So when I am benchmarking, CCMiner uses card 0 twice causing many algos to crash CCminer.  I tried removing the -d list of cards in the startpool.bat file, but then it defaults to 2 cards for benchmarking and mining.  What file can I change to remove the -d card list so the miners just default to all cards?

Any help would be appreciated.  Thanks in advance.

Some of the miners don't support card #11 (10) and think its card #1 (0)
Run NemosMiner on first 8 cards is best (0-7) then have separate batch running against blaze2s, phi, or x17 continuously for other cards using TPruvotcuda9/ccminer 2.2.4 which DOES support -d 8,9,10,11

Thanks!
If I did that would have to have 2 instances of Nemos running?

no you wouldn't
run 24hr script, take note of most profitable miner for your rig
you would then craft a batch file that runs ccminer 2.2.4 for that algo for the extra video cards.
first 8 cards would run nemos, other 4 would run the most profitable from last 24 hours


example batch file: C:\nemosminer-v2.4-master\Bin\NVIDIA-TPruvotcuda9\ccminer.exe -d 8,9,10,11 -a phi -o stratum+tcp://phi.mine.ahashpool.com:8333 -u 1FTyourwallet -p ID=MINER1B,c=BTC