Ninjastic
PostEdited versionsQuotes to this post
Post
Topic
Board Pools (Altcoins)
Re: [POOL] YAAMP.COM multipool multialgo profit switch with exchange
by
chrysophylax
on 05/07/2015, 15:49:07 UTC
Quote from: joblo on July 05, 2015, 03:34:05 PM
Quote from: chrysophylax on July 05, 2015, 01:52:14 PM
Quote from: unklo on July 05, 2015, 01:25:04 PM

i mean yaamp's code, not site, just try and see for yourself,
multialgo switching makes huge difference

i see what you mean ...

on this fact alone - it does seem that way ...

multialgo switching has abrupt changes to contend with and so suffer share rejects everytime the switch happens ...

this is a loss of shares and productivity - even though they are small between switches ... we have seen this happen with our own miners / farm ...

but that is with ANY multialgo multipool - not just yaamp.com ...

look at epsylon3 .. he is one hell of a developer - and now running his own yaamp-coded pool with more algos added ...

it sort of goes to show that if even a seasoned developer like him is willing to look at - setup - and improve the code - then the pool code is still on a reasonably good level ...

nicehash has the same sort of issues ( though they dont mine coins - just divert hashrate ) with multialgo switching ...

so much so - that they devote an entire section on the website to it ...

single algo / single coin pools may be more 'efficient' ( for lack of a better word ) at mining - but we believe that the losses are so minimal thats its close to negligible ...

#crysx

I don't have a problem with rejects upon switching algos on any multipool. I don't use
the pools' multialgo features,  but I also incur the overhead of killing and restarting ccminer.

I don't think there is a truly elegant way to switch algos. The pool signals by disconnecting
so any unsubmitted shares are lost. Whether the miner reports that as a reject is irrelevant,
it's lost work.

To have a seamless algo switch requires a cooperative disconnect where the miner is allowed
to complete the work in progress.




agreed ...

which also means that the miner and stratum need to work hand-in-hand with one another to become as seamless as possible ...

which lends itself to have the miner AND the stratum backend written by the same dev ... or at least devs that work WITH one another on the same level ...

wolf? ... Wink ...

#crysx