bitHopper: Python Pool Hopper Proxy

[paraipan]

Allright I need to throw a noob curveball question.

Ive only now started to test out newer c00w/ed stats page version and wondered what is the user / shares displayed at the bottom left of the stats page or atleast whats the purpose of that.

You and me both.

make that 3

[joulesbeef]

i believe it is so you can point multiple miners at the same hopper

if you use a different username in your guiminer or command line or w/e you use.. it will keep track of each machines share counts

try it.. stop your miner for a second and rename the user on guiminer or w/e.. restart and suddenly you will have a new username keeping track.

edit:There seems to be a huge bug with it.. there is always that annoying blank user with 0 shares.. why wont he go away.. he is messing up my whole screen.

[Clipse]

i believe it is so you can point multiple miners at the same hopper

if you use a different username in your guiminer or command line or w/e you use.. it will keep track of each machines share counts

try it.. stop your miner for a second and rename the user on guiminer or w/e.. restart and suddenly you will have a new username keeping track.

Haha yeh you hit it on the head, thats what its doing.

[paraipan]

i believe it is so you can point multiple miners at the same hopper

if you use a different username in your guiminer or command line or w/e you use.. it will keep track of each machines share counts

try it.. stop your miner for a second and rename the user on guiminer or w/e.. restart and suddenly you will have a new username keeping track.

Haha yeh you hit it on the head, thats what its doing.

nice, didn't know it was implemented, everyday I learn something...

[joulesbeef]

though it is easy to calc, next to it they should put a new field, total est
so you can see the total estimated earnings of each miner.


if you want to do it manually just multiply your shares by 0.0000264725 (this changes with difficulty and is just 50/current difficulty)

and probably a payout section so you can see total eff.

[Clipse]

though it is easy to calc, next to it they should put a new field, total est
so you can see the total estimated earnings of each miner.


if you want to do it manually just multiply your shares by 0.0000264725 (this changes with difficulty and is just 50/current difficulty)

and probably a payout section so you can see total eff.

I think an estimated mhash from each miner(even if miner connects with multiple gpus) would also be nice based on submitted shares timeframe so that you can see how the total mhash is split up between various mining rigs.

On a sidenote, looks like btcpool24 run off with the 2nd block or he is just to lazy to respond in the forum. Json says blocks found:2 yet the site disabled mining. Another gripe I have with btcpool24, this recent block they seem to misreport ~15% of shares less than actually submitted / accepted, wtf .

[c00w]

Slice scheduler now works.
And I just realized that macboys port looks really glarish to me.
Does everyone like that color scheme better or worse?

[simonk83]

though it is easy to calc, next to it they should put a new field, total est
so you can see the total estimated earnings of each miner.


if you want to do it manually just multiply your shares by 0.0000264725 (this changes with difficulty and is just 50/current difficulty)

and probably a payout section so you can see total eff.

I think an estimated mhash from each miner(even if miner connects with multiple gpus) would also be nice based on submitted shares timeframe so that you can see how the total mhash is split up between various mining rigs.

On a sidenote, looks like btcpool24 run off with the 2nd block or he is just to lazy to respond in the forum. Json says blocks found:2 yet the site disabled mining. Another gripe I have with btcpool24, this recent block they seem to misreport ~15% of shares less than actually submitted / accepted, wtf .

Yes I noticed the share discrepancies as well.

[Clipse]

Slice scheduler now works.
And I just realized that macboys port looks really glarish to me.
Does everyone like that color scheme better or worse?

The idea originally sounded nice but after trying it for few mins I wanted to puke

[Clipse]

For those in the know-how, how to get btcguild(default mining) and deepbit(backup mining) working the way it did before the pool / user config splits.

I used this in the old pool.py and it worked out pretty good for me but have no clue how to get the same structure in the pools.cfg to make it work the same again:

btcguild - Current btcguild code isnt fixed to read the correct shares location.

Code:

    def btcg_sharesResponse(self, response):
        parsed = response.replace('\n', '').replace('\r','').replace('\t','')
        outputTime = re.search('<span id=\"last_announce_time\" class=\"header_stat\">([:0-9]*)</span></td>', parsed)
        outputSpeed = re.search('<span id="pool_speed" class="header_stat">([ 0-9\.]*)GH/s', parsed)
        if outputTime != None and outputSpeed != None:
            server = self.servers['btcg']
            extractTime = outputTime.group(1).split(':')
            roundTime = int(extractTime[0])*60*60 + int(extractTime[1])*60 + int(extractTime[2])
            server['ghash'] = float(outputSpeed.group(1).replace(' ',''))
            server['duration'] = roundTime
            round_shares = int( server['ghash'] * roundTime / 4)
            self.UpdateShares('btcg',round_shares, True)
        else:
            self.bitHopper.log_msg('regex fail : btcg')

deepbit

Code:

    def deepbit_sharesResponse(self, response):
        round_shares = self.bitHopper.difficulty.get_btc_difficulty()*0.431
        self.UpdateShares('deepbit',round_shares)

[muyoso]

On a sidenote, looks like btcpool24 run off with the 2nd block or he is just to lazy to respond in the forum. Json says blocks found:2 yet the site disabled mining. Another gripe I have with btcpool24, this recent block they seem to misreport ~15% of shares less than actually submitted / accepted, wtf .

Just post this:

http://www.youtube.com/watch?v=6Pv9oRxPOIc

[simonk83]

Slice scheduler now works.
And I just realized that macboys port looks really glarish to me.
Does everyone like that color scheme better or worse?

Right, now we seem to be working     Quick thought though, would be it worth disabling the slicing when on Slush, as you're only on there till 10% anyway which tends to be over pretty quickly.

[ed64]

Thanks, try my latest pull, the one i posted was flaky, couldn't get it to slice predictably, maybe you can look at it? I tried to simplify...

As for jumping pools, with the getwork store now, it doesn't seem to be much of an issue, even when i switched pools every 30s or so when using a small slice size for testing... I did add in a min slice size option to prevent too frequent hopping though.

So for some reason it likes to get stuck on BTCPool24.

yep, something is not right, 40593 seconds from beginning of the round (11 hours) at 30Gh on average (have seen 50Gh+), has only 288422 shares...

Try my AltSliceScheduler: https://github.com/echiu64/bitHopper
Use options like

Code:

--scheduler AltSliceScheduler --altslicesize=1200

Default is 600 "slice" or "pie" size, in that the 600 will be divided amongst the pools, weighted by their share count.

For really fast switch set it to 60. Takes about a minute or so to wait for all the stats to initialize and have the slice redistribution get set. Not sure if there is a better way to trigger this earlier.

Still using the previous stats page for the alt slice scheduler, so should be functional...

You can see the time slice count on the stats page as well and will decrement over time. The next largest slice will be selected. Once all are exhausted, slices are recalculated...

Credit goes to flowers for the original implementation

really nice! thank you very much for that.

just a little suggestion:

if "reslice" occurs don't take the pool with the biggest slice. instead check if the current pool got another slice and if so stay there -> reducing hopping a little and worked well for me (i changed it in a later version, so you might not have catched it up).

i'll switch to your version now. do you want me to make the suggestion as a pull request? its really not much

[joulesbeef]

is it really worth hopping btcguild? with the hour delay?.. how are you working out when to hop? are you just saying like 23% takes an hr and adjusting what you think the shares should be in reality bashed on their total mh?


and the btcpool24 guy says they found a block but his payment going to take time cause he is a crappy coder or something like that.. they are also changing the proportional equation which in my boat means something other than prop

i'm just going to leave them disabled until my account has a ballance

[ed64]

Sorry for the funky slice merge, the latest AltSliceScheduler works well, tested it for a few hours, looks good to me, hopped everything it was supposed to and switched to eligius.st when pools became unhoppable.

For the round time scheduler, I'm looking to add in Ryouiki's algorithm from his fork, as yet another way of hopping. His hopping may be more invasive, so I've left it for last.

In the meantime, I like his idea of adding a "penalty" option for each pool. Rather than have "mine" and "mine_slush" we add in penalty: 1.5 for say ozco.in if they delay stats or something like that.

In Ryouiki's UI, he has the ability to manually change the penalty. He's also enhanced his hopping algorithm with a feedback loop to adjust penalties on the fly...

Also remove "role: mine" from pools.cfg if you have having issues disabling bloodys....

[Clipse]

Sorry for the funky slice merge, the latest AltSliceScheduler works well, tested it for a few hours, looks good to me, hopped everything it was supposed to and switched to eligius.st when pools became unhoppable.

For the round time scheduler, I'm looking to add in Ryouiki's algorithm from his fork, as yet another way of hopping. His hopping may be more invasive, so I've left it for last.

In the meantime, I like his idea of adding a "penalty" option for each pool. Rather than have "mine" and "mine_slush" we add in penalty: 1.5 for say ozco.in if they delay stats or something like that.

In Ryouiki's UI, he has the ability to manually change the penalty. He's also enhanced his hopping algorithm with a feedback loop to adjust penalties on the fly...

Also remove "role: mine" from pools.cfg if you have having issues disabling bloodys....

Yeh, I love the ryo dynamic penalty system, waiting for that to get added to c00w's version or your fork

[simonk83]

Also remove "role: mine" from pools.cfg if you have having issues disabling bloodys....

Ah ha, what's that doing in there  Thanks

[Clipse]

is it really worth hopping btcguild? with the hour delay?.. how are you working out when to hop? are you just saying like 23% takes an hr and adjusting what you think the shares should be in reality bashed on their total mh?

With ryo's fork using dynamic penality, deepbit(backup) and btcguild(based on poolspeed it actually worked out positive jumping in even with the hour delayed stats). Im not going to discuss the efficiency level before someone spams btcg owner with this post. Lets just say its +EV so far.

[simonk83]

EDIT2:  Ok, found the culprit (I assume):

2011-08-03 13:22:40: Listener for "Hopper2": [03/08/2011 13:22:40] Connected to server
2011-08-03 13:27:06: Listener for "Hopper2": [03/08/2011 13:27:06] Warning: work queue empty, miner is idle
2011-08-03 13:27:10: Listener for "Hopper": [03/08/2011 13:27:10] Warning: work queue empty, miner is idle
2011-08-03 13:34:17: Listener for "Hopper": [03/08/2011 13:34:17] Warning: work queue empty, miner is idle
2011-08-03 13:34:22: Listener for "Hopper2": [03/08/2011 13:34:22] Warning: work queue empty, miner is idle
2011-08-03 13:34:59: Listener for "Hopper": [03/08/2011 13:34:59] LP: New work pushed
2011-08-03 13:34:59: Listener for "Hopper2": [03/08/2011 13:34:59] LP: New work pushed
2011-08-03 13:35:14: Listener for "Hopper": [03/08/2011 13:35:14] Warning: work queue empty, miner is idle

Right, with these dropouts I've been having, it's definitely a problem with bloody's.   It only ever happens on that server.   Not sure why it only happens to me and not others, but there you go.  I'm in Australia so I guess distance is a factor, but then it would be with the majority of the other pools as well and they're fine

[Clipse]

Ed, I see you defined mine_slush at 0.4*difficulty, is that correct afaik it should be something between 0.10 - 0.25 if I remember correctly.