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

Plus Nicehack can operate at a loss until they need some more funds to continue then organise a convenient wallet hack… 

Consider how is it possible (beyond consistent luck +/- getting the best of fluctuating exchange rates) that a pool can consistently out earn the calculated amount at whattomine when WTM considers net hash rate of the entire algorithm across all pools. Also consider that WTM and other calculators are likely ideal earnings; multi algorithm pools often use PPLNS or some PPLNS hybrid which doesn't favor algorithm switching as compared to PPS of nicehash. In other words, what you see is typically what you get with nicehash compared to the ideal earnings on WTM.

If WTM has nicehash near 90% of the top algorithms it's going to be tough to beat especially if hopping from algorithm to algorithm on a multi-algo pool. For example, x17 is the top algorithm on ahash pool and the listed estimates don't even come close to nicehash's rates.

I've gone back to single pool mining vs nicehash.

I suppose as educated miners we have to keep all our options open. I am doing a 24-Hour test with four machines on NH to see how it comes out for me.

I certainly won't store any coins with NH but I may try their service again -- also the NEMO front-end for NH is nice as well... not so bloated like the NH software.

Maybe, but considering that an errant powershell script can literally destroy a Windows installation, not really.

Look at the substance of what I wrote: there is not even a basic description of what NemosMiner does in the first post. It is *assumed* by the OP that everyone knows what a multi-pool miner does. Well, maybe that is true at the so-called "30,000 foot level", but I still want to know the details like, where is the data from API polling stored, where/how is that data manipulated, how are errors handled like, say, a benchmark failing (one of my test rigs was basically idled for 8+ hours because "timetravel" failed... that's dumb no matter how you slice it), how are miners configured, hell, what does every switch in the pool batch files do!?, etc... None of that is explained either in the first post or on the "github" - more on that below.


It's not that I am unsympathetic to your position - indeed, I always read the first 2-3 and last 2-3 pages of a thread before asking a (potentially stupid) question - but after *decades* of using forums (starting with BBSes, USENET, etc...) I have a fairly keen sense of how things ought to proceed in matters like this, and the first post is by far the best place to put updates. Github is a relatively new creation, and besides, few ever bother to write a decent readme.md file for their git repository, anyway. See, for example, the SGMiner-GM github with a readme.md that is 4+ years old. Seriously?

Could use a little help... just switched to 2.4.2 I have 5 gigabyte 1070 G1's and a gigabyte 1070TI. Any suggestions on what miners to use. I'm on Mining pool Hub.
clocks are 85% 100/400 holding steady no crashes(yet)...
With V2.4.1 I was getting:
DSTM=Equihash 2.82 kh/s <----crashed a lot on overclocking
ccminertpruvotx64=Lyra2z 10.48 mh/s
EthashClaymore=ethash 150.50mh/s
ccminerpolytimos=Lyra2RE2 241.61 mh/s
V2.4.2
ccminertpruvox64=equihash 2.24 kh/s
ccminertpruvox64=Lyra2z 9.84 mh/s
ccminertpruvox64=skein 2.30 gh/s
ccminertpruvox64Lyra2RE2= 226.69 mh/s
ccminerKlaust=neroscrypt= 6.71 mh/s

Don't you think this is more demeaning and more of a dick move than my snarky statement?


I don't expect anyone or everyone to read all 3000+ posts, but if there's recent buzz about a new patch, you'd think the changelog is nearby. In addition, almost any competent dev has the changelog on their Github, it's standard practice.

Well, I'm still waiting for an explanation of what, precisely, this collection of half-assed scripts does, so it's no surprise the first post wasn't updated with a changelog.

And btw, pointing someone to post #3421 and asking rhetorically, "not sure where you've been looking" is kind of a dick move. While we can all fantasize about every one reading 3000+ post threads before asking a question, that's just flatly unrealistic, so let's not pretend otherwise, mmm?

? Not sure where you've been looking.

https://bitcointalksearch.org/topic/m.30312532

https://github.com/nemosminer/NemosMiner-v2.4.2/releases

Nemo, can you please type up a quick changelog on the first page when you release an update? It's impossible to track or know the differences otherwise. What have you changed/improved between v2.4.1 and v2.4.2?

Palgin with neoscrypt probably.. disable palgin miner ps1 (delete file) and edit klaust miner file to uncomment neoscrypt

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...

Believe me, after all the trash talking I've done about NiceHash (aka NiceHack), no one was more surprised as each and every multi-algo pool I've tested over the last month has come in 2nd place, and often by a startling amount. HashRefinery and Zergpool both brought in 30% less over their 1 week test period than NH. Granted, both pools happened to get on the wrong side of some hard-forks, but since that isn't something you have to worry about with NH I can't really toss out the comparisons as invalid. Both MiningPoolHub and Zpool came in around 10% less than NH over their test periods (1 week for MPH, only 3 days for Zpool) and given the limitations of my test setup I am inclined to call these a tie, but that's rather missing the point: the whole idea behind multi-algo, auto-switching pools is to beat single-coin mining AND NiceHash over time (if you are the type that either cashes out in fiat on a regular basis or just wants to accumulate BTC without buying a shitty ASIC).

And especially since NH is rather restricted in the algos it offers I am even more surprised at the poor showing of these multi-algo pools, but maybe it's not the pool's fault, maybe it's NemosMiner's, so I am contemplating trying another multi-algo miner manager next.

Claymore tries to use all gpu's not that ones specified in the .bat file.  Is this normal behavior.  Thanks

Forgot to add.  Blazepool 24hr does not seem accurate at all.  Stuck mining Blake2s for 2+ hrs, switched to non 24hr script and blake2s was one of the least profitable coins

So your deleting the bat files to delete the pools or is there some where else.
EDIT: Delete from the pool folder, Got it...
2ndEDIT: neoscrypt, should I ?

yes, same with pools, I delete all the pools I don't use so the system isn't grabbing stats for pools I don't need.  I delete the PalginHSR because it never seems to work properly on any of the 24 rigs I manage and edit the Klaust to enable neoscrypt.

If I want to use a certain miner in NM, is all I have to do is delete/hide the miners I don't want to use that are in the miner folder?
EDIT: The reason I ask is I have 1 rig 6x 1070 and I only mine eqihash,Lyra2RE2,ethash and Lyra2z, and want to use 1 miner. does this make sense? thanks

I have been away from NH for quite a while now (last year when I compared ZPOOL was ahead of NH for me) -- but I fired it up on two workers to size it up again.

Early impression is that the profit seems quite high right now on NiceHash -- probably due to the "bull market" run we are having (e.g. people willing to pay above market for the power).

If I knew what the top 6 algos were at any given moment I wouldn't need NemosMiner?!? I could just make the usual rolling list of ccminer, etc., command line entries in a batch file and loop through them every 60s (or whatever)!

I may well give ahashpool a shot (using the plus version of the batch file) but as of now I don't really have enough hashpower to make me comfortable trying out a pool with a 0.01 BTC minimum payout. I did take note of your test results, but I'd like to see how ahashpool compares with NiceHash, because so far every single one of these multi-algo pools has lost out to the 800lb gorilla.

It makes more sense to add them all and let the app determine the most profitable.

You are missing some very profitable algos on that list.....  x17 is rocking it right now.  blake2s and skein should be added as well