[DEAD] DeepBit.net PPS+Prop,instant payouts, we pay for INVALID BLOCKS too

[[Tycho]]

Any idea how I can get long polling working? There's no extra flags required to enable it, correct?

Tell me your login name so can check it at my side.
What is hashing speed of your miners ?

BTW, if you see a stale hash instantly after "new block" message, it means that your miner sent it's result just some milliseconds before or after LP notify, so it's normal. But 2% is definitely not normal for Long Polling. Is this number decreasing now or not ?

[nster]

I get 0.6~0.7 stale share with LP I believe. Not bad, but not perfect

[[Tycho]]

I get 0.6~0.7 stale share with LP I believe. Not bad, but not perfect

It's very hard to get stales percentage lower than 0.3% because of network delay.
And it depends on your hashing speed too. Your result is normal.

[slush]

I get 0.6~0.7 stale share with LP I believe. Not bad, but not perfect

Nothing is perfect and LP don't lead to absolute zero of stale shares; there are still latencies in server broadcasts, on network level, miner have to refresh his job internally etc. I think 0.3% is the minimum which can be done with current infrastructure, so 0.6% isn't SO bad.

Btw I'm thinking that better number for showing LP effectivity should be (stale shares)/(new blocks notifications), which tell us in how many cases was the LP broadcast too late. It is more exact than (stale shares)/(submitted shares), because this number depends also on bitcoin network speed (difficulty and hashrate) and when new blocks are coming faster or slower than before, this number will be affected. What do you think, Tycho?

[JWU42]

I am at .19% stale 

Two crappy days in a row with 11 and 10 blocks found, respectively.

[jaybob20]

I run find for a bit and then get these "errors" and it stops submitting new blocks. I set my timeout to 15. Any ideas?

16/03/2011 01:17:07, 310189 khash/s
16/03/2011 01:17:07, d3eab41a, accepted
16/03/2011 01:17:08, 310087 khash/s
....
16/03/2011 01:17:50, 310167 khash/s
16/03/2011 01:17:50, 18364559, accepted
16/03/2011 01:17:51, 310008 khash/s
....
16/03/2011 01:18:14, 310228 khash/s
16/03/2011 01:18:14, Wrong data: checkWork: this nonce already completed
16/03/2011 01:18:15, 310012 khash/s
.....
16/03/2011 01:19:28, 309955 khash/s
16/03/2011 01:19:29, long poll: new block
16/03/2011 01:19:29, 302538 khash/s
.....
16/03/2011 01:24:45, 309991 khash/s
16/03/2011 01:24:45, Wrong data: checkWork: this nonce already completed
16/03/2011 01:24:46, 309802 khash/s
....
16/03/2011 01:29:24, 309983 khash/s
16/03/2011 01:29:24, Wrong data: checkWork: No record for this data, please set
lower getwork timeout (5 seconds)
16/03/2011 01:29:26, 309819 khash/s
.....
16/03/2011 01:30:41, 309976 khash/s
16/03/2011 01:30:42, Wrong data: checkWork: No record for this data, please set
lower getwork timeout (5 seconds)
16/03/2011 01:30:43, 309700 khash/s

[m0mchil]

... I set my timeout to 15 ...

What are your command line options? How do you set the timeout?

[jaybob20]

... I set my timeout to 15 ...

What are your command line options? How do you set the timeout?

python poclbm.py -d0 --host=deepbit.net --port=8332 --user=xxxxxxx --pass=xxxxxx -v -w 128 --verbose
I also lowered the clocks on my card to minimums to see if that was making things strange.
I also removed the frames flag.

I set the timeout in the python fileBitcoinMiner.py TIMEOUT = 15, I did that after having problems, and I'm still getting problems.
I have the latest git pull from a day ago.


17/03/2011 08:56:34, 225438 khash/s
17/03/2011 08:56:34, Stale hash. To reduce stales, use long polling, e.g. latest m0mchil's python miner
17/03/2011 08:56:35, 225269 khash/s
I am...

Repeates about every 30 seconds:
17/03/2011 09:00:55, Wrong data: checkWork: No record for this data, please set lower getwork timeout (5 seconds)

[Dr. Arnold]

Tell me your login name so can check it at my side.
What is hashing speed of your miners ?

BTW, if you see a stale hash instantly after "new block" message, it means that your miner sent it's result just some milliseconds before or after LP notify, so it's normal. But 2% is definitely not normal for Long Polling. Is this number decreasing now or not ?

My login is jakiedentures (at) gmail.com
I get ~300 MH/s on my 6950 and ~70 MH/s on my 4850. The stale share % has not gone down and is sitting at 0.93% and 2.47% respectively

[[Tycho]]

UPDATES:

• Shares and stale counters can be reset, all at once or one at a time (total sum is still saved).
• Now you can delete workers if you don't need them anymore

[JWU42]

Nearing 12 hours without a block?!?

[[Tycho]]

Nearing 12 hours without a block?!?

No need to worry, it's already averaged out by a run of easy blocks :)

[sniper_sniperson]

Since 2 days my balance is not transfered to the wallet. No contact information at deepbit.net site...

[[Tycho]]

Since 2 days my balance is not transfered to the wallet. No contact information at deepbit.net site... ::)

What is your login ? White it here or PM me.
Your balance should be transferred each day if it's over your threshold and you have your address configured.

I found a couple of users with word "sniper" in login. If the one with ~6.95 balance is you, then you just get 0.01 over your threshold today.
Payment is sent.


Currently i'm modifying payment system. Tomorrow there should appear "Pay now" button for that :)

[JWU42]

Nice new feature 

[sniper_sniperson]

Yep, it's ok now (0.00360724 BTC current). Where can I check the current balance of the wallet ?

[os008]

Use the Bitcoin application to check your wallet. It should update it automatically.

[[Tycho]]

Hello, CPU miners.

New version of jgarzik's CPU mining software supports long polling now, so you can improve your efficiency by installing it.
Please upgrade.

[BitLex]

..so you can improve your efficiency by installing it.
Please upgrade.

sorry to say, but...well, long polling actually isn't as efficient as you want it to be.
no idea what it's like for others, or on other pools, with long polling i get ~0.90% stale shares, without long polling i get ~1.05% stale shares.

that's not really much of an improvement.

[[Tycho]]

..so you can improve your efficiency by installing it. Please upgrade.

sorry to say, but...well, long polling actually isn't as efficient as you want it to be.
no idea what it's like for others, or on other pools, with long polling i get ~0.90% stale shares, without long polling i get ~1.05% stale shares.
that's not really much of an improvement.

Overall effect is very noticeable to me, many GPU miners are submitting only 0.2 - 1% of stales.
Don't know yet what is the cause for some others, including you, but it will be especially useful for CPU miners because of their low hashrate.
I'm trying to resolve this issue, but not done yet, sorry.

Two of my fastest users at this moment submit 0.14% and 0.16% of stales, most of the "top5" are in 0.2-0.6% range.
For comparison, users of poclbm-mod are in 3.05%-4.44% (and one with 35%, but he does something really wrong)

EDIT: looks like I see something like a bug in your miner's answer.
BTW, you are using two different miners - "poclbm/201103.beta" and "poclbm/20110311" on same worker account. Can you please create two new workers and place those miners on each one separately, so i can see which one is faulty ?