[1500 TH] p2pool: Decentralized, DoS-resistant, Hop-Proof pool

[rav3n_pl]

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.

[lenny_]

Yep, +600 MB of RAM (after 1hours of running, newest from git) usage make it absolutely unusable on my 1GB RAM machine.

[Subo1977]

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.

for me on Linux all is ok with this build.
Node uptime: 0.322 days, 306M P2Pool, 204M Bitcoind

[PatMan]

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.

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

[Schleicher]

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)

[PatMan]

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)

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

[BR0KK]

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):

What does this mean?

[mdude77]

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)

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

[PatMan]

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)

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.

[mdude77]

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.

That's not too much off.  You should get about 3 shares an hour.  The orphans suck though.

M

[forrestv]

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!

[mdude77]

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!

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

[Ed]

P2Pool release 9.1

upgraded

still a lot of wasted work, about 2 times more that before v.9 hardfork happened

[mdude77]

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!

After about 7 hours @ ~4.8GH/s:

46 shares, 9 orphaned, 3 dead, 26% stale rate.  Not any better.  But I was asleep, I can't tell if I had my normal connection problems over night.  Might not be p2pool's fault.

In other news, pool hash is < 300GH/s, making my slice of the pie bigger.  Now if we can just get a block or two before the great halving occurs.

M

[PatMan]

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!

Thanks Forrestv - checking it out now, stay tooned.

[twmz]

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!

It's probably not been long enough for this to be statistically valid, but things look better for me (prior to this version I was closer to 20% stale rate):

Code:

 P2Pool: 17355 shares in chain (17359 verified/17359 total) Peers: 30 (24 incoming)
  Local: 1610MH/s in last 10.0 minutes Local dead on arrival: ~1.8% (0-5%) Expected time to share: 28.7 minutes
  Shares: 18 (0 orphan, 1 dead) Stale rate: ~5.6% (0-26%) Efficiency: ~117.8% (92-124%) Current payout: 0.2555 BTC
  Pool: 365GH/s Stale rate: 19.8% Expected time to block: 11.2 hours

We'll see how things look after another 24-48 hours.

[PatMan]

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!

It's probably not been long enough for this to be statistically valid, but things look better for me (prior to this version I was closer to 20% stale rate):

Code:

 P2Pool: 17355 shares in chain (17359 verified/17359 total) Peers: 30 (24 incoming)
  Local: 1610MH/s in last 10.0 minutes Local dead on arrival: ~1.8% (0-5%) Expected time to share: 28.7 minutes
  Shares: 18 (0 orphan, 1 dead) Stale rate: ~5.6% (0-26%) Efficiency: ~117.8% (92-124%) Current payout: 0.2555 BTC
  Pool: 365GH/s Stale rate: 19.8% Expected time to block: 11.2 hours

We'll see how things look after another 24-48 hours.

That's looking better, even though it is early doors. How did you manage to get connected to so many peers (30 &24 in)? I've never managed to get above 11 & 0 in.....

[rav3n_pl]

ng better, even though it is early doors. How did you manage to get connected to so many peers (30 &24 in)? I've never managed to get above 11 & 0 in.....

Code:

usage: run_p2pool.exe [-h] [--version] [--net {bitcoin,litecoin}] [--testnet]
                      [--debug] [-a ADDRESS] [--datadir DATADIR]
                      [--logfile LOGFILE] [--merged MERGED_URLS]
                      [--give-author DONATION_PERCENTAGE] [--iocp]
                      [--irc-announce] [--no-bugreport] [--p2pool-port PORT]
                      [-n ADDR[:PORT]] [--disable-upnp] [--max-conns CONNS]
                      [--outgoing-conns CONNS] [-w PORT or ADDR:PORT]
                      [-f FEE_PERCENTAGE]
                      [--bitcoind-address BITCOIND_ADDRESS]
                      [--bitcoind-rpc-port BITCOIND_RPC_PORT]
                      [--bitcoind-rpc-ssl]
                      [--bitcoind-p2p-port BITCOIND_P2P_PORT]
                      [BITCOIND_RPCUSERPASS [BITCOIND_RPCUSERPASS ...]]

(...)
  --max-conns CONNS     maximum incoming connections (default: 40)
  --outgoing-conns CONNS
                        outgoing connections (default: 6)

You need also open port 9333 to accept incoming.

[PatMan]

ng better, even though it is early doors. How did you manage to get connected to so many peers (30 &24 in)? I've never managed to get above 11 & 0 in.....

Code:

usage: run_p2pool.exe [-h] [--version] [--net {bitcoin,litecoin}] [--testnet]
                      [--debug] [-a ADDRESS] [--datadir DATADIR]
                      [--logfile LOGFILE] [--merged MERGED_URLS]
                      [--give-author DONATION_PERCENTAGE] [--iocp]
                      [--irc-announce] [--no-bugreport] [--p2pool-port PORT]
                      [-n ADDR[:PORT]] [--disable-upnp] [--max-conns CONNS]
                      [--outgoing-conns CONNS] [-w PORT or ADDR:PORT]
                      [-f FEE_PERCENTAGE]
                      [--bitcoind-address BITCOIND_ADDRESS]
                      [--bitcoind-rpc-port BITCOIND_RPC_PORT]
                      [--bitcoind-rpc-ssl]
                      [--bitcoind-p2p-port BITCOIND_P2P_PORT]
                      [BITCOIND_RPCUSERPASS [BITCOIND_RPCUSERPASS ...]]

(...)
  --max-conns CONNS     maximum incoming connections (default: 40)
  --outgoing-conns CONNS
                        outgoing connections (default: 6)

You need also open port 9333 to accept incoming.

Right, thanks rav3n, but 9333 is already open. Is there a reason why the defaults are 40 & 6? And would there be any benefit in changing them?

Still a noob, still learning......

[cabin]

Right, thanks rav3n, but 9333 is already open. Is there a reason why the defaults are 40 & 6? And would there be any benefit in changing them?

Still a noob, still learning......

The more nodes you connect to the faster your shares reach the entire network and the fewer stales you will have. But if you are on a home internet connection you don't want to saturate your upload bandwidth because that will just mess everything up and Bitcoin needs to take a chunk of bandwidth too. So try to strike a balance that suits your connection.