P2Pool release 9.1
upgradedstill a lot of wasted work, about 2 times more that before v.9 hardfork happened
Topic: [1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool - page 615. (Read 2591920 times)
November 28, 2012, 01:31:34 AM
still a lot of wasted work, about 2 times more that before v.9 hardfork happened
November 27, 2012, 10:15:30 PM
P2Pool release 9.1 tag: 9.1 hash: 9742ead60733e26f94ee10a16c43ee7cb403e88c
Windows binary: http://u.forre.st/u/fngdrqsq/p2pool_win32_9.1.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/9.1
Source tarball: https://github.com/forrestv/p2pool/tarball/9.1
Changes:
* Don't connect to older nodes and ignore old shares
This release is a test to see whether it mitigates the high stale proportion the pool is seeing. Please use it and report if things improve for you!
Windows binary: http://u.forre.st/u/fngdrqsq/p2pool_win32_9.1.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/9.1
Source tarball: https://github.com/forrestv/p2pool/tarball/9.1
Changes:
* Don't connect to older nodes and ignore old shares
This release is a test to see whether it mitigates the high stale proportion the pool is seeing. Please use it and report if things improve for you!
Thanks!
Upgraded. I'll post in the morning how things are going.
BTW, my earlier statement about unit value decreasing on p2pool, I forgot about the increased difficulty, the expected unit value is there.
M
November 27, 2012, 09:52:29 PM
P2Pool release 9.1 tag: 9.1 hash: 9742ead60733e26f94ee10a16c43ee7cb403e88c
Windows binary: http://u.forre.st/u/fngdrqsq/p2pool_win32_9.1.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/9.1
Source tarball: https://github.com/forrestv/p2pool/tarball/9.1
Changes:
* Don't connect to older nodes and ignore old shares
This release is a test to see whether it mitigates the high stale proportion the pool is seeing. Please use it and report if things improve for you!
Windows binary: http://u.forre.st/u/fngdrqsq/p2pool_win32_9.1.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/9.1
Source tarball: https://github.com/forrestv/p2pool/tarball/9.1
Changes:
* Don't connect to older nodes and ignore old shares
This release is a test to see whether it mitigates the high stale proportion the pool is seeing. Please use it and report if things improve for you!
November 27, 2012, 09:15:32 PM
Lucky you, since my reboot over 3 hours ago I've had 7 shares, 3 of which are orphaned........on a 2.3gig setup.......this is hurting.
EDIT: Make that 8 shares and 4 orphaned.......it's too much man.
EDIT: Make that 8 shares and 4 orphaned.......it's too much man.
That's not too much off. You should get about 3 shares an hour. The orphans suck though.
M
November 27, 2012, 09:06:35 PM
No worky for me on win7 64. New git doesn't load the shares & cgminer don't connect.....
Works fine here, but I use Python, not the compiled version:Code:
2012-11-27 22:39:37.696000 Pool: 352GH/s Stale rate: 27.3% Expected time to block: 11.7 hours
2012-11-27 22:39:38.764000 New work for worker! Difficulty: 0.999985 Share difficulty: 572.519064 Total block value: 50.916300 BTC including 306 transactions
2012-11-27 22:39:40.706000 P2Pool: 17419 shares in chain (9436 verified/17423 total) Peers: 7 (1 incoming)
2012-11-27 22:39:38.764000 New work for worker! Difficulty: 0.999985 Share difficulty: 572.519064 Total block value: 50.916300 BTC including 306 transactions
2012-11-27 22:39:40.706000 P2Pool: 17419 shares in chain (9436 verified/17423 total) Peers: 7 (1 incoming)
Got it working after a reboot.
This stale rate is painful watching, how much longer do you think it will take to settle down again? 25-30% is a lot of wasted work.....
Despite the high stales, p2pool seems to be continuing to work as normal. We got 2 blocks today already, which is above average.
This morning the stale rate was at 15%. That and seeing that the old version shares will be gone from the chain convinced me to rejoin. I'm running at 21% stale atm, which is a little below the pool. I've been on for about 13.5 hours. At 9.5 minutes a share, I should have about 86 shares. I have 99, 15 of which are orphan, 6 are dead, which is pretty good considering I'm having ISP problems that causes me to lose packets every so often.
Now if we can get just that patch we were promised...
M
Lucky you, since my reboot over 3 hours ago I've had 7 shares, 3 of which are orphaned........on a 2.3gig setup.......this is hurting.
EDIT: Make that 8 shares and 4 orphaned.......it's too much man.
November 27, 2012, 08:04:45 PM
No worky for me on win7 64. New git doesn't load the shares & cgminer don't connect.....
Works fine here, but I use Python, not the compiled version:Code:
2012-11-27 22:39:37.696000 Pool: 352GH/s Stale rate: 27.3% Expected time to block: 11.7 hours
2012-11-27 22:39:38.764000 New work for worker! Difficulty: 0.999985 Share difficulty: 572.519064 Total block value: 50.916300 BTC including 306 transactions
2012-11-27 22:39:40.706000 P2Pool: 17419 shares in chain (9436 verified/17423 total) Peers: 7 (1 incoming)
2012-11-27 22:39:38.764000 New work for worker! Difficulty: 0.999985 Share difficulty: 572.519064 Total block value: 50.916300 BTC including 306 transactions
2012-11-27 22:39:40.706000 P2Pool: 17419 shares in chain (9436 verified/17423 total) Peers: 7 (1 incoming)
Got it working after a reboot.
This stale rate is painful watching, how much longer do you think it will take to settle down again? 25-30% is a lot of wasted work.....
Despite the high stales, p2pool seems to be continuing to work as normal. We got 2 blocks today already, which is above average.
This morning the stale rate was at 15%. That and seeing that the old version shares will be gone from the chain convinced me to rejoin. I'm running at 21% stale atm, which is a little below the pool. I've been on for about 13.5 hours. At 9.5 minutes a share, I should have about 86 shares. I have 99, 15 of which are orphan, 6 are dead, which is pretty good considering I'm having ISP problems that causes me to lose packets every so often.
Now if we can get just that patch we were promised...
M
November 27, 2012, 06:05:51 PM
Code:
31.090000 Pool: 363GH/s Stale rate: 24.7% Expected time to block: 11.3 hours
34.093000 P2Pool: 17381 shares in chain (17386 verified/25649 total) Peers: 10 (0 incoming)
12.125000 Local: 3906MH/s in last 10.0 minutes Local dead on arrival: ~37.1% (33-42%) Expected time to share: 11.0 minutes
12.125000 Shares: 72 (5 orphan, 25 dead) Stale rate: ~41.7% (30-54%) Efficiency: ~77.5% (62-92%) Current payout: 0.2347 BTC
12.125000 Pool: 363GH/s Stale rate: 24.7% Expected time to block: 11.3 hours
12.171000 Punishing share for 'Block-stale detected! 2c90fb1f86f221fb9bca83576678db89ad63abd7f27bb75ed47 < 4be47f3f97213111c964eef6b0358452e2220ba747274a08242'! Jumping from 8af96802
12.250000 Punishing share for 'Block-stale detected! 2c90fb1f86f221fb9bca83576678db89ad63abd7f27bb75ed47 < 4be47f3f97213111c964eef6b0358452e2220ba747274a08242'! Jumping from 293a6771
12.312000 Punishing share for 'Block-stale detected! 2c90fb1f86f221fb9bca83576678db89ad63abd7f27bb75ed47 < 4be47f3f97213111c964eef6b0358452e2220ba747274a08242'! Jumping from fa6826c2
12.375000 Punishing share for 'Block-stale detected! 2c90fb1f86f221fb9bca83576678db89ad63abd7f27bb75ed47 < 4be47f3f97213111c964eef6b0358452e2220ba747274a08242'! Jumping from a21c717a
12.406000 Peer sent entire transaction that was already received
12.421000 Peer sent entire transaction that was already received
12.437000 Peer sent entire transaction that was already received
12.437000 Peer sent entire transaction that was already received
12.453000 Peer sent entire transaction that was already received
12.453000 Peer sent entire transaction that was already received
12.484000 Peer sent entire transaction that was already received
12.515000 Peer sent entire transaction that was already received
12.546000 Peer sent entire transaction that was already received
12.546000 Peer sent entire transaction that was already received
12.578000 Peer sent entire transaction that was already received
12.578000 Peer sent entire transaction that was already received
12.625000 Punishing share for 'Block-stale detected! 2c90fb1f86f221fb9bca83576678db89ad63abd7f27bb75ed47 < 4be47f3f97213111c964eef6b0358452e2220ba747274a08242'! Jumping from a21c717a
12.765000 Punishing share for 'Block-stale detected! 2c90fb1f86f221fb9bca83576678db89ad63abd7f27bb75ed47 < 4be47f3f97213111c964eef6b0358452e2220ba747274a08242'! Jumping from a21c717a
15.562000 Punishing share for 'Block-stale detected! 2c90fb1f86f221fb9bca83576678db89ad63abd7f27bb75ed47 < 4be47f3f97213111c964eef6b0358452e2220ba747274a08242'! Jumping from 30d4d9e5
15.593000 Peer sent entire transaction that was already received
15.609000 Peer sent entire transaction that was already received
15.625000 New work for worker! Difficulty: 0.999985 Share difficulty: 606.493564 Total block value: 50.000000 BTC including 0 transactions
15.640000 Peer sent entire transaction that was already received
15.640000 Peer sent entire transaction that was already received
15.640000 Peer sent entire transaction that was already received
15.656000 Peer sent entire transaction that was already received
15.671000 > Error getting work from bitcoind:
15.671000 > Traceback (most recent call last):
34.093000 P2Pool: 17381 shares in chain (17386 verified/25649 total) Peers: 10 (0 incoming)
12.125000 Local: 3906MH/s in last 10.0 minutes Local dead on arrival: ~37.1% (33-42%) Expected time to share: 11.0 minutes
12.125000 Shares: 72 (5 orphan, 25 dead) Stale rate: ~41.7% (30-54%) Efficiency: ~77.5% (62-92%) Current payout: 0.2347 BTC
12.125000 Pool: 363GH/s Stale rate: 24.7% Expected time to block: 11.3 hours
12.171000 Punishing share for 'Block-stale detected! 2c90fb1f86f221fb9bca83576678db89ad63abd7f27bb75ed47 < 4be47f3f97213111c964eef6b0358452e2220ba747274a08242'! Jumping from 8af96802
12.250000 Punishing share for 'Block-stale detected! 2c90fb1f86f221fb9bca83576678db89ad63abd7f27bb75ed47 < 4be47f3f97213111c964eef6b0358452e2220ba747274a08242'! Jumping from 293a6771
12.312000 Punishing share for 'Block-stale detected! 2c90fb1f86f221fb9bca83576678db89ad63abd7f27bb75ed47 < 4be47f3f97213111c964eef6b0358452e2220ba747274a08242'! Jumping from fa6826c2
12.375000 Punishing share for 'Block-stale detected! 2c90fb1f86f221fb9bca83576678db89ad63abd7f27bb75ed47 < 4be47f3f97213111c964eef6b0358452e2220ba747274a08242'! Jumping from a21c717a
12.406000 Peer sent entire transaction that was already received
12.421000 Peer sent entire transaction that was already received
12.437000 Peer sent entire transaction that was already received
12.437000 Peer sent entire transaction that was already received
12.453000 Peer sent entire transaction that was already received
12.453000 Peer sent entire transaction that was already received
12.484000 Peer sent entire transaction that was already received
12.515000 Peer sent entire transaction that was already received
12.546000 Peer sent entire transaction that was already received
12.546000 Peer sent entire transaction that was already received
12.578000 Peer sent entire transaction that was already received
12.578000 Peer sent entire transaction that was already received
12.625000 Punishing share for 'Block-stale detected! 2c90fb1f86f221fb9bca83576678db89ad63abd7f27bb75ed47 < 4be47f3f97213111c964eef6b0358452e2220ba747274a08242'! Jumping from a21c717a
12.765000 Punishing share for 'Block-stale detected! 2c90fb1f86f221fb9bca83576678db89ad63abd7f27bb75ed47 < 4be47f3f97213111c964eef6b0358452e2220ba747274a08242'! Jumping from a21c717a
15.562000 Punishing share for 'Block-stale detected! 2c90fb1f86f221fb9bca83576678db89ad63abd7f27bb75ed47 < 4be47f3f97213111c964eef6b0358452e2220ba747274a08242'! Jumping from 30d4d9e5
15.593000 Peer sent entire transaction that was already received
15.609000 Peer sent entire transaction that was already received
15.625000 New work for worker! Difficulty: 0.999985 Share difficulty: 606.493564 Total block value: 50.000000 BTC including 0 transactions
15.640000 Peer sent entire transaction that was already received
15.640000 Peer sent entire transaction that was already received
15.640000 Peer sent entire transaction that was already received
15.656000 Peer sent entire transaction that was already received
15.671000 > Error getting work from bitcoind:
15.671000 > Traceback (most recent call last):
What does this mean?
November 27, 2012, 04:55:34 PM
No worky for me on win7 64. New git doesn't load the shares & cgminer don't connect.....
Works fine here, but I use Python, not the compiled version:Code:
2012-11-27 22:39:37.696000 Pool: 352GH/s Stale rate: 27.3% Expected time to block: 11.7 hours
2012-11-27 22:39:38.764000 New work for worker! Difficulty: 0.999985 Share difficulty: 572.519064 Total block value: 50.916300 BTC including 306 transactions
2012-11-27 22:39:40.706000 P2Pool: 17419 shares in chain (9436 verified/17423 total) Peers: 7 (1 incoming)
2012-11-27 22:39:38.764000 New work for worker! Difficulty: 0.999985 Share difficulty: 572.519064 Total block value: 50.916300 BTC including 306 transactions
2012-11-27 22:39:40.706000 P2Pool: 17419 shares in chain (9436 verified/17423 total) Peers: 7 (1 incoming)
Got it working after a reboot.
This stale rate is painful watching, how much longer do you think it will take to settle down again? 25-30% is a lot of wasted work.....
November 27, 2012, 04:48:03 PM
No worky for me on win7 64. New git doesn't load the shares & cgminer don't connect.....
Works fine here, but I use Python, not the compiled version:Code:
2012-11-27 22:39:37.696000 Pool: 352GH/s Stale rate: 27.3% Expected time to block: 11.7 hours
2012-11-27 22:39:38.764000 New work for worker! Difficulty: 0.999985 Share difficulty: 572.519064 Total block value: 50.916300 BTC including 306 transactions
2012-11-27 22:39:40.706000 P2Pool: 17419 shares in chain (9436 verified/17423 total) Peers: 7 (1 incoming)
2012-11-27 22:39:38.764000 New work for worker! Difficulty: 0.999985 Share difficulty: 572.519064 Total block value: 50.916300 BTC including 306 transactions
2012-11-27 22:39:40.706000 P2Pool: 17419 shares in chain (9436 verified/17423 total) Peers: 7 (1 incoming)
November 27, 2012, 02:42:24 PM
Latest git 0f89cbab18 (9.0-16-g0f89cba) seems work good for me - no freezes and no doas.
Only dat memory consumption...
Win32 build on my skydrive if s1 want to try.
Only dat memory consumption...
Win32 build on my skydrive if s1 want to try.
for me on Linux all is ok with this build.
Node uptime: 0.322 days, 306M P2Pool, 204M Bitcoind
No worky for me on win7 64. New git doesn't load the shares & cgminer don't connect.....
November 27, 2012, 05:40:18 AM
Latest git 0f89cbab18 (9.0-16-g0f89cba) seems work good for me - no freezes and no doas.
Only dat memory consumption...
Win32 build on my skydrive if s1 want to try.
Only dat memory consumption...
Win32 build on my skydrive if s1 want to try.
for me on Linux all is ok with this build.
Node uptime: 0.322 days, 306M P2Pool, 204M Bitcoind
November 27, 2012, 05:30:44 AM
Yep, +600 MB of RAM (after 1hours of running, newest from git) usage make it absolutely unusable on my 1GB RAM machine.
November 27, 2012, 05:26:39 AM
Latest git 0f89cbab18 (9.0-16-g0f89cba) seems work good for me - no freezes and no doas.
Only dat memory consumption...
Win32 build on my skydrive if s1 want to try.
Only dat memory consumption...
Win32 build on my skydrive if s1 want to try.
November 26, 2012, 09:25:01 PM
There is pool software you could setup but theres no point and its very difficult. Its just like solo mining which you could do just with regular bitcoin client. Depending on how many singles you have, it could be a good choice. But until we get the new SC singles which should work with p2pool, just use a regular pool like slushs.
November 26, 2012, 09:03:31 PM
ok, so I will remove it.
are there any other pool server I can set up to work on own servers?
are there any other pool server I can set up to work on own servers?
November 26, 2012, 08:59:53 PM
DO NOT use bfl singles with p2pool
November 26, 2012, 08:47:24 PM
Things should get better tomorrow when the last of the old shares fall off the end of the sharechain and I make a new release that fixes several critical issues.
ok lets see
hope it will work better tomorrow.
if yes, I will set up a new pool for bitcoin-24.com
November 26, 2012, 08:41:24 PM
Hey,
I have now run p2pool + miner for about 10 minutes.
Are this stats normal?
I have a lot of rejected shares.
http://i.imagebanana.com/img/69p4jvda/Bildschirmfoto20121127um02.31.22.png
http://i.imagebanana.com/img/54xmi7v6/Bildschirmfoto20121127um02.31.36.png
BFL Singles don't really work with p2pool. I have now run p2pool + miner for about 10 minutes.
Are this stats normal?
I have a lot of rejected shares.
http://i.imagebanana.com/img/69p4jvda/Bildschirmfoto20121127um02.31.22.png
http://i.imagebanana.com/img/54xmi7v6/Bildschirmfoto20121127um02.31.36.png
November 26, 2012, 08:36:44 PM
Things should get better tomorrow when the last of the old shares fall off the end of the sharechain and I make a new release that fixes several critical issues.
November 26, 2012, 08:33:36 PM
Hey,
I have now run p2pool + miner for about 10 minutes.
Are this stats normal?
I have a lot of rejected shares.
I have now run p2pool + miner for about 10 minutes.
Are this stats normal?
I have a lot of rejected shares.
Jump to: