bitHopper: Python Pool Hopper Proxy - page 92.

djex

full member

Activity: 196

Merit: 100

Quote from: simonk83 on August 03, 2011, 08:23:12 PM

Ok, so now I'm trying ed64's and the slicing is working.

However, Slush is being ignored now Sad

They just reset to zero and I'm sitting on MtRed.

Wooooah. Just got a massive list of errors and it crapped out. Didn't get a chance to save the error unfortunately. Back to c00w's methinks...

I'm using ed's and it's been working great for about 45 min now. You have the latest?

simonk83

hero member

Activity: 798

Merit: 1000

Ok, so now I'm trying ed64's and the slicing is working.

However, Slush is being ignored now Sad

They just reset to zero and I'm sitting on MtRed.

Wooooah. Just got a massive list of errors and it crapped out. Didn't get a chance to save the error unfortunately. Back to c00w's methinks...

simonk83

hero member

Activity: 798

Merit: 1000

Quote from: joulesbeef on August 03, 2011, 08:14:26 PM

wait when was "backup_latehop" added.. what does it do versus backup? just makes sure you dont use the percents? is this c00ws or ed64? what

c00w's (well, both I guess).

In the user.cfg.default it says:

#backup_latehop = prefers this for backup if PPS pool
has high share count, recommended for all backups

joulesbeef

sr. member

Activity: 476

Merit: 250

moOo

wait when was "backup_latehop" added.. what does it do versus backup? just makes sure you dont use the percents? is this c00ws or ed64? what

djex

full member

Activity: 196

Merit: 100

Quote from: simonk83 on August 03, 2011, 07:37:43 PM

Bloody's is available (28%) but it's just sticking to MtRed.

Same here.

Edit: Just switched to ed64's fork. Working good so far.

simonk83

hero member

Activity: 798

Merit: 1000

Quote from: paraipan on August 03, 2011, 07:34:56 PM

Quote from: simonk83 on August 03, 2011, 07:30:37 PM

Quote from: paraipan on August 03, 2011, 07:26:54 PM

Quote from: simonk83 on August 03, 2011, 07:19:53 PM

Let me just make sure I'm reading this right. I should basically be enabling ALL the backup pools and setting them all to backup_latehop?

not all, only the backup pools you use

Ok, even the PPS ones?

As far as the slicing goes, I've disabled BTCPool24 and it's now just been stuck on MtRed for 15 mins or so. I don't think it's working Wink

PPS pool should be used as backup always, you're stuck on mt.red if is the only prop pool available, seems to be working allright

Bloody's is available (28%) but it's just sticking to MtRed.

paraipan

legendary

Activity: 924

Merit: 1004

Firstbits: 1pirata

Quote from: simonk83 on August 03, 2011, 07:30:37 PM

Quote from: paraipan on August 03, 2011, 07:26:54 PM

Quote from: simonk83 on August 03, 2011, 07:19:53 PM

Let me just make sure I'm reading this right. I should basically be enabling ALL the backup pools and setting them all to backup_latehop?

not all, only the backup pools you use

Ok, even the PPS ones?

As far as the slicing goes, I've disabled BTCPool24 and it's now just been stuck on MtRed for 15 mins or so. I don't think it's working Wink

PPS pool should be used as backup always, you're stuck on mt.red if is the only prop pool available, seems to be working allright

simonk83

hero member

Activity: 798

Merit: 1000

Quote from: paraipan on August 03, 2011, 07:26:54 PM

Quote from: simonk83 on August 03, 2011, 07:19:53 PM

Let me just make sure I'm reading this right. I should basically be enabling ALL the backup pools and setting them all to backup_latehop?

not all, only the backup pools you use

Ok, even the PPS ones?

As far as the slicing goes, I've disabled BTCPool24 and it's now just been stuck on MtRed for 15 mins or so. I don't think it's working Wink

paraipan

legendary

Activity: 924

Merit: 1004

Firstbits: 1pirata

Quote from: djex on August 03, 2011, 07:25:49 PM

Is polmine.pl down for anyone else?

yep, down here too, ozco is back, mt.red got a lucky one, and btcpool24 posibly faking stats (collecting info) EXTRA

edit: btcpool24 changed their payout system with an unknown one and their json stats seem to have a life of their own

dribbits

newbie

Activity: 20

Merit: 0

Quote from: djex on August 03, 2011, 07:25:49 PM

Is polmine.pl down for anyone else?

Yep, not working here either.

paraipan

legendary

Activity: 924

Merit: 1004

Firstbits: 1pirata

Quote from: simonk83 on August 03, 2011, 07:19:53 PM

Let me just make sure I'm reading this right. I should basically be enabling ALL the backup pools and setting them all to backup_latehop?

not all, only the backup pools you use

djex

full member

Activity: 196

Merit: 100

Is polmine.pl down for anyone else?

simonk83

hero member

Activity: 798

Merit: 1000

Let me just make sure I'm reading this right. I should basically be enabling ALL the backup pools and setting them all to backup_latehop?

owowo

newbie

Activity: 43

Merit: 0

c00w <3 just a small thingy, BTCworld.de shows up in the bitHopper-page as BTCworld.COM a little confusing... ;o)

flower1024

legendary

Activity: 1428

Merit: 1000

Quote from: ed64 on August 03, 2011, 06:56:54 PM

Quote from: paraipan on August 03, 2011, 06:50:05 PM

Quote from: djex on August 03, 2011, 06:37:54 PM

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

paraipan

legendary

Activity: 924

Merit: 1004

Firstbits: 1pirata

Quote from: simonk83 on August 03, 2011, 06:57:01 PM

Quote from: paraipan on August 03, 2011, 06:50:05 PM

Quote from: djex on August 03, 2011, 06:37:54 PM

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

So disable it for now you reckon?

I did

just trying to find out if they're scr...g with us

simonk83

hero member

Activity: 798

Merit: 1000

Quote from: paraipan on August 03, 2011, 06:50:05 PM

Quote from: djex on August 03, 2011, 06:37:54 PM

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

So disable it for now you reckon?

ed64

newbie

Activity: 42

Merit: 0

Quote from: paraipan on August 03, 2011, 06:50:05 PM

Quote from: djex on August 03, 2011, 06:37:54 PM

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

paraipan

legendary

Activity: 924

Merit: 1004

Firstbits: 1pirata

Quote from: djex on August 03, 2011, 06:37:54 PM

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

muyoso

member

Activity: 84

Merit: 10

OK, testing out the latest c00w now.

Pools at at:

MtRed 7%
Bitcoins.lc 26%
BTCpool24 15%
Bitclockers 33%

Started mining at MtRed. Will keep track of what it does by editing this comment.

Edit:

After 8 minutes it jumped from MtRed to Bitclockers.

Aaaaaaaaaaaaaaand then it mined on bitclockers for 15 minutes never switching again. Also, threw multiple errors for the first time ever from bithopper in my miner:

Code:

Deferred:
Unhandled Error
Traceback (most recent call last):
  File "twisted\internet\defer.pyc", line 361, in callback

  File "twisted\internet\defer.pyc", line 455, in _startRunCallback

  File "twisted\internet\defer.pyc", line 542, in _runCallbacks

  File "twisted\internet\defer.pyc", line 1076, in gotResult

---  ---
  File "twisted\internet\defer.pyc", line 1020, in _inlineCallbacks

  File "minerutil\RPCProtocol.pyc", line 226, in _requestComplete

  File "minerutil\RPCProtocol.pyc", line 319, in handleWork

exceptions.TypeError: argument of type 'NoneType' is not iterable

Topic: bitHopper: Python Pool Hopper Proxy - page 92. (Read 355678 times)