Yo Ed, last time I will bother you but please tell me if this is the intended functionality of your altslice set to 1200 .
- It remains on pools until slice time runs out, no matter if a pool is >43.5% or in case of mine_slush >~11%, it will continue until timeslice is finish.
- If there is a new server with fresh block and that server have a timeslice assigned to it, it would jump to a timeslice on higher shares server ie. bitclockers were at 0% and timesliced at 600s whereas bloody is at 35% and timesliced at 600 aswell, now what happened it moved from btcpool24(finished timeslice there) and jumped to bloody and not bitclockers?
If this is the way it should work, Id like to understand this method better cause I cant for the life of me figure out how this could be more profitable than hop lowest share or dynamic penalty+hop lowest share.
Yes that's the intended behaviour. Try the latest pull, I (bone headedly) weighted based on most shares and not least shares, so that should fix your issue... stupid mistake! - It remains on pools until slice time runs out, no matter if a pool is >43.5% or in case of mine_slush >~11%, it will continue until timeslice is finish.
- If there is a new server with fresh block and that server have a timeslice assigned to it, it would jump to a timeslice on higher shares server ie. bitclockers were at 0% and timesliced at 600s whereas bloody is at 35% and timesliced at 600 aswell, now what happened it moved from btcpool24(finished timeslice there) and jumped to bloody and not bitclockers?
If this is the way it should work, Id like to understand this method better cause I cant for the life of me figure out how this could be more profitable than hop lowest share or dynamic penalty+hop lowest share.
