Topic: [UNRESPONSIVE POOL OPERATOR] 50BTC.com - page 63. (Read 257845 times)
What is closest other pool as far as low fee PPS?
No worries. It is hashing away just nicely, dont panic TM
Same deal here, for now packing my mining gear to use of other pool with less problems and better informing in case there are some. Good luck, hope there's some ideas why miners are having these problems.
Any news from operators would be appreciated. I ended up trying another pool ATM.
But would love to go back to 50BTC if i could get speeds back, and invalids not going crazy to often.
But would love to go back to 50BTC if i could get speeds back, and invalids not going crazy to often.
Anyone else getting a lot of stale shares the last couple of days? I'm getting about 18-25% invalid shares now on 8 rigs running on BAMT. It was always in the low 1-2% range.
Yeah, I have. There seems to be some trouble with the pool the last couple days. Web site becomes unavailable for a while, miners dropping off to backup pools many times a day. I'm sure they are trying to fix it.
I switched to a back up pool at BTCGuild and have 0% stale or invalid on all 8 rigs for at least a hour now. So it's definitely something to do with 50BTC pool. I will switch back when the problem is resolved.
yes, I am also experiencing some problems the last cople days. lot of invalids, also, my worker disconnects a lot.
any news, updates from pool operator?
since 15:50 dashboard shows 0 MH but worker is connected an gets work?
??
??That happens from time to time. Check that your balance increases at the expected rate. The worker stats and graphs should come back on track after a while.
since 15:50 dashboard shows 0 MH but worker is connected an gets work???
?? 
[ ... ]
*John is dizzy from the math*
I'm running at around 8.5GH/s for now, and I want to submit say 13 shares per minute, I'll need to choose diff 8, right?
Try this for an explanation of how and why share difficulty affects your income, and what settings you should use.
*John is dizzy from the math*
I'm running at around 8.5GH/s for now, and I want to submit say 13 shares per minute, I'll need to choose diff 8, right? Yep, which will amount to about +/- 9% hourly variation.
What is the optimal share amount per minute?
It all depends on you. If there's no need to reduce your bandwidth at your end, then by choosing a higher difficulty you're increasing your variance to help the pool reduce its bandwidth usage.
Pick an amount that you're happy with - in the long run (say a few days) even at D32 you wont notice much variance. It's only a problem if you're trying to match the pools' estimate of your hashrate with your local estimate.
Ah, okay, thanks for the advice.
[ ... ]
*John is dizzy from the math* I'm running at around 8.5GH/s for now, and I want to submit say 13 shares per minute, I'll need to choose diff 8, right?
Try this for an explanation of how and why share difficulty affects your income, and what settings you should use.
*John is dizzy from the math*
I'm running at around 8.5GH/s for now, and I want to submit say 13 shares per minute, I'll need to choose diff 8, right? Yep, which will amount to about +/- 9% hourly variation.
What is the optimal share amount per minute?
It all depends on you. If there's no need to reduce your bandwidth at your end, then by choosing a higher difficulty you're increasing your variance to help the pool reduce its bandwidth usage.
Pick an amount that you're happy with - in the long run (say a few days) even at D32 you wont notice much variance. It's only a problem if you're trying to match the pools' estimate of your hashrate with your local estimate.
Okay, here we go again....
Worker is dead.
Worker is dead.
Have you tried connecting to the pool nearest you, rather than the general url. I'm in UK so have pool-de, then pool-ru then pool-us
24 Hours
150,000 shares, 9 invalids, < 0.1% Rejects and payments are almost exactly what they should be for hashrate (and it's been like this for weeks, no problems except web page)
Whoa, I didn't know there was specific pools for different regions. I'll try to connect to the nearest pool for me.
Try this for an explanation of how and why share difficulty affects your income, and what settings you should use.
*John is dizzy from the math*
I'm running at around 8.5GH/s for now, and I want to submit say 13 shares per minute, I'll need to choose diff 8, right? What is the optimal share amount per minute?Thanks everyone!
Okay, here we go again....
Worker is dead.
Worker is dead.
Have you tried connecting to the pool nearest you, rather than the general url. I'm in UK so have pool-de, then pool-ru then pool-us
24 Hours
150,000 shares, 9 invalids, < 0.1% Rejects and payments are almost exactly what they should be for hashrate (and it's been like this for weeks, no problems except web page)
Try this for an explanation of how and why share difficulty affects your income, and what settings you should use.
30 min shares (invalid): 821 (715) 
Okay, here we go again....
Worker is dead.
Worker is dead.
It consists of 11 FPGA's at around 840 MH/s each, connected to the pool via a single stratum proxy. Hmm... I changed the diff to 4, and the numbers seem correct again. My 24 H speed and 24 H earned seems way off though... 
Wait for 24 hours to see how the change impacts performance long-term.
In the meantime, the 60-minute shares should give a fair indication if the change helped.EDIT: I would treat each board as a separate miner, follow this table
Worker's speed Difficulty
<500 Mhash/s 1
500- 1000Mhash/s 2
1000-2000Mhash/s 4
2000-4000Mhash/s 8
4000-10000Mhash/s 16
10000-40000Mhash/s 32
>40000Mhash/s 64
and would keep the difficulty at 2, even though they are all behind the same proxy. Work shares get distributed between the boards, and it might be so that they do not manage to process higher-difficulty shares in time, turning up a large number of invalids...
It is my guess, though. It would be nice if a pool admin elaborated on share difficulty in multi-card/multi-board scenarios.
I ran them nicely now at 4. Wasn't sure if that's the solution here, but it's working anyway.
Thanks!
It consists of 11 FPGA's at around 840 MH/s each, connected to the pool via a single stratum proxy. Hmm... I changed the diff to 4, and the numbers seem correct again. My 24 H speed and 24 H earned seems way off though...
Wait for 24 hours to see how the change impacts performance long-term.
In the meantime, the 60-minute shares should give a fair indication if the change helped.EDIT: I would treat each board as a separate miner, follow this table
Worker's speed Difficulty
<500 Mhash/s 1
500- 1000Mhash/s 2
1000-2000Mhash/s 4
2000-4000Mhash/s 8
4000-10000Mhash/s 16
10000-40000Mhash/s 32
>40000Mhash/s 64
and would keep the difficulty at 2, even though they are all behind the same proxy. Work shares get distributed between the boards, and it might be so that they do not manage to process higher-difficulty shares in time, turning up a large number of invalids...
It is my guess, though. It would be nice if a pool admin elaborated on share difficulty in multi-card/multi-board scenarios.
I ran my 9~ GH/s farm at 8 diff. I'll try modifying it to 4 and see later then.
Does your farm consist of 1 unit á 9GH/s or 18 units (cards) á 500MH/s?
One of my machines has 2x7970 churning out 1.3GH/s, yet I still treat it as 2 units, producing ~600MH/s + ~700MH/s, assigned to two different workers on the pool, each set to diff. 1 shares.
I now restarted cgminer, associated with that card which started to spike with invalids (cgminer also reported an increasing number of R's), and it is back to normal - the increase stopped. I guess I will slightly reduce the restartEvery setting in my Bitcoin Miners in Tray front-end so that restarts and therefore refreshes of the miners' states would occur more often.
Can you please share your settings you are using?
Are you using a backup pool or anything of thiers? Also what port just 3333?
Are you using a backup pool or anything of thiers? Also what port just 3333?
I use cgminer with a front-end of my own writing.
The settings are (this machine has 6670 + 7970, and this setting is for device 0):
-T -l 2 -I d,9 -d 0 --gpu-engine 920,1150 --gpu-memclock 925,1375 --gpu-fan 50,84 -o http://pool.50btc.com:3333 -u username_machine6670 -p password -o http://pool80.50btc.com -u username_machine6670 -p password -o http://eu.ozco.in:3333 -u username.machine6670 -p password
It consists of 11 FPGA's at around 840 MH/s each, connected to the pool via a single stratum proxy. Hmm... I changed the diff to 4, and the numbers seem correct again. My 24 H speed and 24 H earned seems way off though...
I ran my 9~ GH/s farm at 8 diff. I'll try modifying it to 4 and see later then.
Does your farm consist of 1 unit á 9GH/s or 18 units (cards) á 500MH/s?
One of my machines has 2x7970 churning out 1.3GH/s, yet I still treat it as 2 units, producing ~600MH/s + ~700MH/s, assigned to two different workers on the pool, each set to diff. 1 shares.
I now restarted cgminer, associated with that card which started to spike with invalids (cgminer also reported an increasing number of R's), and it is back to normal - the increase stopped. I guess I will slightly reduce the restartEvery setting in my Bitcoin Miners in Tray front-end so that restarts and therefore refreshes of the miners' states would occur more often.
Can you please share your settings you are using?
Are you using a backup pool or anything of thiers? Also what port just 3333?
Are you using a backup pool or anything of thiers? Also what port just 3333?
I use cgminer with a front-end of my own writing.
The settings are (this machine has 6670 + 7970, and this setting is for device 0):
-T -l 2 -I d,9 -d 0 --gpu-engine 920,1150 --gpu-memclock 925,1375 --gpu-fan 50,84 -o http://pool.50btc.com:3333 -u username_machine6670 -p password -o http://pool80.50btc.com -u username_machine6670 -p password -o http://eu.ozco.in:3333 -u username.machine6670 -p password
What is your share's difficulty setting?
I tried setting it to 2 for 7970 cards (per their advice for miners with >500MH/s power), but I noticed that it negatively affected my performance, so now I am back to level 1 for all cards.
EDIT: One card had a spike of 33 (and counting) invalids over the last hour, so my 24-hour stats are now 46463 (35) cumulative for all cards.
I tried setting it to 2 for 7970 cards (per their advice for miners with >500MH/s power), but I noticed that it negatively affected my performance, so now I am back to level 1 for all cards.
EDIT: One card had a spike of 33 (and counting) invalids over the last hour, so my 24-hour stats are now 46463 (35) cumulative for all cards.
Can you please share your settings you are using?
Are you using a backup pool or anything of thiers? Also what port just 3333?
Ive tried a few things.... my speed ultimately goes down. Never gets up to proper speed. And eventually invalids just go crazy.
Growing pains from it moving from 17 to 19+ so quick? If anyone finds solutions please help with ideas.
Growing pains from it moving from 17 to 19+ so quick? If anyone finds solutions please help with ideas.
Jump to: