bitHopper: Python Pool Hopper Proxy

[joulesbeef]

I dont get that high in rejects.. maybe 6% with bitclockers.. it does go red often and kick me off, so i dont get many shares there.

which pool you on.. yeah I'm sure you tried them all.. but which one.

and what is with bitcoin.lc.. i guess they are delaying stats but giving us the right stats? seemed to never hit zero but was suddenly 30%

[1714198202]

1714198202

[1714198202]

1714198202

[1714198202]

1714198202

[1714198202]

1714198202

[organofcorti]

I dont get that high in rejects.. maybe 6% with bitclockers.. it does go red often and kick me off, so i dont get many shares there.

which pool you on.. yeah I'm sure you tried them all.. but which one.

and what is with bitcoin.lc.. i guess they are delaying stats but giving us the right stats? seemed to never hit zero but was suddenly 30%

I'm using pools 1 2 and 3 concurrently.

It was getting so bad that I even tried a 1 share altslice between the three servers - I put a worker on each server and gave them the names bitclockers bitclockers2 etc as if they were actually different pools. I tried to just server a share at a time to each pool hoping it would slow down my getwork rate and fix stales. This got my stales down to 20 - 25%. Not nearly good enough.

re bclc - even if they are delaying, mining from say 30 to 43% is still more efficient than mining PPS. SO don't worry about it - in the long run missing a little from one pool is no big deal.

[simonk83]

I've totally given up with bitclockers until we work out what the problem is.    If it works ok in Cherry Picker then I guess it's something in the bitHopper code.

[hawks5999]

Data point on biclockers:
With Cherry: .513% stales.
2.3Gh/s on one worker from 10 GPUs
Same account and worker since before I started hopping.
FWIW.

[creativex]

Using Altslicer, Slush currently on 14%, still requesting work...

EDIT:  Stopped it manually at 18% as I'm heading out and don't trust it to stop on its own.  Regardless, it's not quite working as intended yet.

Sounds like it was actually set to mine rather than mine_slush for some reason. I heard of someone else having that problem back a few pages. I just caught the current block at slush's and it stop slicing right at 11% so it does work at least part of the time. Catching those really quick blocks with such a small time investment is gold.

[flower1024]

Data point on biclockers:
With Cherry: .513% stales.
2.3Gh/s on one worker from 10 GPUs
Same account and worker since before I started hopping.
FWIW.

with my poclbm mod i am running at 0.28% and 0.33% stales (only twominers running).

and still using the nicer stats grabbing and pool decisions from bitthopper

[joulesbeef]

with my poclbm mod i am running at 0.28% and 0.33% stales (only twominers running).

and still using the nicer stats grabbing and pool decisions from bitthopper

so you arent using cherry picker.. just modded poclbm and bithopper?

[flower1024]

with my poclbm mod i am running at 0.28% and 0.33% stales (only twominers running).

and still using the nicer stats grabbing and pool decisions from bitthopper

so you arent using cherry picker.. just modded poclbm and bithopper?

yes,

my poclbm-mod connects to bithopper and loads a pool list from there.

it checks the page every three seconds and switches (with no stale or rejects) to the new bithopper-current

you'll lose the worker management and submitted shares display in bithopper (and it sometimes shows an exception on a flaky connection - which could safely be ignored [just had no time to fix it right now])

btw. i am working on this atm: http://miner.k1024.de
its pre pre pre alpha. only thing that works:
a nice stats page where two bithopper instances pushes their round share information.
they are both running on different networks - just to make sure the pools dont start playing "whats your ip" with us

(suggestions are welcome)

[joulesbeef]

neat i have some questions but I'll put it in your thread

[simonk83]

Using Altslicer, Slush currently on 14%, still requesting work...

EDIT:  Stopped it manually at 18% as I'm heading out and don't trust it to stop on its own.  Regardless, it's not quite working as intended yet.

Sounds like it was actually set to mine rather than mine_slush for some reason. I heard of someone else having that problem back a few pages. I just caught the current block at slush's and it stop slicing right at 11% so it does work at least part of the time. Catching those really quick blocks with such a small time investment is gold.

It was definitely set to mine_slush

[Starlightbreaker]

i just realized something weird.

I run two bithoppers on two different rigs, exact same bithopper, ran with altslicer...one hops to deepbit, the other one to polmine.
restarted the bithopper, same thing.


what's going on? 

[djex]

i just realized something weird.

I run two bithoppers on two different rigs, exact same bithopper, ran with altslicer...one hops to deepbit, the other one to polmine.
restarted the bithopper, same thing.


what's going on? 

Ahh the joys of programming. Code an application, works great on the computer its coded on but then gives different results on each different computer its on. It's probably one of those things where you have a different version of something and its just slightly different. Like possibly different version of twisted on each computer.

[organofcorti]

i just realized something weird.

I run two bithoppers on two different rigs, exact same bithopper, ran with altslicer...one hops to deepbit, the other one to polmine.
restarted the bithopper, same thing.


what's going on? 

Ahh the joys of programming. Code an application, works great on the computer its coded on but then gives different results on each different computer its on. It's probably one of those things where you have a different version of something and its just slightly different. Like possibly different version of twisted on each computer.

Or maybe the little green men that run around inside the computer have slightly different preferences. What, you didn't know there were tiny people in your computer? Why do you think cpus and gpus get so hot then? With all those tiny bodies getting hot running around they need lots of aircon, and that's why we have fans and water cooling.

Sorry this is slightly off topic but it's important for people to understand the basics of computing.

cheers

ooc

[djex]

Or maybe the little green men that run around inside the computer have slightly different preferences. What, you didn't know there were tiny people in your computer? Why do you think cpus and gpus get so hot then? With all those tiny bodies getting hot running around they need lots of aircon, and that's why we have fans and water cooling.

Sorry this is slightly off topic but it's important for people to understand the basics of computing.

cheers

ooc

No no I agree, its fundamental that people understand how computers work. One thing you left out though is that you can accidentally drown the green men if you use water cooling and if you do that its game over. Need to make sure its not too deep for them when your setting it up.

Again off topic, but it's a good tip

[organofcorti]

Or maybe the little green men that run around inside the computer have slightly different preferences. What, you didn't know there were tiny people in your computer? Why do you think cpus and gpus get so hot then? With all those tiny bodies getting hot running around they need lots of aircon, and that's why we have fans and water cooling.

Sorry this is slightly off topic but it's important for people to understand the basics of computing.

cheers

ooc

No no I agree, its fundamental that people understand how computers work. One thing you left out though is that you can accidentally drown the green men if you use water cooling and if you do that its game over. Need to make sure its not too deep for them when your setting it up.

Again off topic, but it's a good tip

Yes. very good point. Too much water means they'll either drown, or grow pot and smoke it - either way they stop working, in the latter case with a puff of smoke.

One last tip and I promise I'll post anything else I think is useful under 'hardware'. Always remember to have birth control available for your Little Green Men (computer 'pros' call them LGM). Daily prices for these miniature condoms can be found at lgm.gov.my:

http://www3.lgm.gov.my/mre/daily.aspx

[Starlightbreaker]

i just realized something weird.

I run two bithoppers on two different rigs, exact same bithopper, ran with altslicer...one hops to deepbit, the other one to polmine.
restarted the bithopper, same thing.


what's going on? 

Ahh the joys of programming. Code an application, works great on the computer its coded on but then gives different results on each different computer its on. It's probably one of those things where you have a different version of something and its just slightly different. Like possibly different version of twisted on each computer.

both are exactly the same version of twisted, openssl, and zope.

eh, i guess it's just part of the fun.

[djex]

Yes. very good point. Too much water means they'll either drown, or grow pot and smoke it - either way they stop working, in the latter case with a puff of smoke.

One last tip and I promise I'll post anything else I think is useful under 'hardware'. Always remember to have birth control available for your Little Green Men (computer 'pros' call them LGM). Daily prices for these miniature condoms can be found at lgm.gov.my:

http://www3.lgm.gov.my/mre/daily.aspx

Very good tip. I've been looking for a site like this for awhile now. The last one got shut down for having bugs in their product. It was horrible.

Oh and before I start a new post in hardware I'd like to say that getting insurance for your little green men is a good idea. Rates and pricing can be found at: http://www.lgm.ca/

both are exactly the same version of twisted, openssl, and zope.

eh, i guess it's just part of the fun.

I found with these sorts of things it's best to just blame it on ridiculous events such as possibly one to many dogs expelled gas at that very moment you installed bitHopper and caused a ripple in time forever changing the future.

[Starlightbreaker]

i'm quite positive it's because of the germs in the laundry basket, where i set up the rig.

damn germs, messing with my bits & bytes.

[hawks5999]

Data point on biclockers:
With Cherry: .513% stales.
2.3Gh/s on one worker from 10 GPUs
Same account and worker since before I started hopping.
FWIW.

with my poclbm mod i am running at 0.28% and 0.33% stales (only twominers running).

and still using the nicer stats grabbing and pool decisions from bitthopper

Cool I'll have to check it out. Dies it work with ryouiki fork or just c00w's?

I think it reinforces that bithopper is still identifiable by bitclockers when it's in between.

[GenTarkin]

The behaviour I experience w/ bithopper and slush, latest build is...
Default start values (no switches) and also mine_slush, penalty 4.0

bh stops mining slush around 3% into around =/

Is this right? how can I fix it?
Thanks