merc82, no answers, so I ask another one:
small diff coins vs big pool power.
GDN 1.09G
JUG 1.33G
QBC 517.12M
MultPort (1.86Ghash/s)
When pool switch to coins its BOOOOM, nuclear bomb to mosquito, pool catch blocks very fast. It's profatible, but only for small part of miners.
Then pool jump to another coin by scoring algorythm.
This fash switching algorythm good cause coin difficulty not grown up to the moon. But as You can see fast switching bad for end-miners cause frequent reconnect/reject/stale and efficiency drop down. Example: pool switch to GDN, I see reconnect, block,block,block, reconnect switch to DRK. NO ONE SHARE SEND AT ALL BY ME and many other workers in minute. Small coins do not need big pool power, it's superfluity.
What
we You can do? Maybe do two multipool worker for each algo scrypt/nscrypt/x11? Split (Random distribute) miners via two group/two pool workers (maybe use us/eu servers as worker groups?), two pool workers still switch via scoring algorythm in turn.
Scoring algorythm select next coins to switch, then
if (target coin nethash < pool hashpower) {
# switch only one pool worker in turn to coin
if (lasts_switched_worker == 1) { switch pool_worker2; last_switched_worker=2} else {switch pool_worker1; last_switched_worker=1}
}else {
switch pool_worker1;
switch pool_worker2;
}Why No? Maybe It's more effectively, so more profatible (and to You). No one multipool have power and effectivity adjustment, You can.
