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

[sharky112065]

I'm just trying out p2pool for first time.

I'm getting a lot of these:

Traceback (most recent call last):
Failure: twisted.python.failure.DefaultException: sharereply result: too long

Is that normal or is something wrong?

In cgminer it always say the pool is dead. But I'm entering apparently correct values.

netstat -lntp shows it's listening on 0.0.0.0 not 127.0.0.1

9.3 fixed this problem. Scroll up.

Ah. Ok. I didn't read back much. I'll d/l and try 9.3 then. Thx.

edit: Done. That error is gone. But the pool still shows as Dead in cgminer.

Using,
host: http://127.0.0.1:9332
user: 15...address
pwd: xxx

It should work as the stats/graph interface shows up on 127.0.0.1:9332

edit2:
Or does it just always take a while after starting p2pool for it to be alive? I see it now shows up as alive in cgminer after about 10 minutes or so.

Now I'm getting this:

Code:

[2012-12-05 12:54:22] Rejected e26cbf8f.5ca9c8b1 GPU 0 pool 3
 [2012-12-05 12:54:29] Accepted 70721a13.01ba3366 GPU 1 pool 3
 [2012-12-05 12:54:34] LONGPOLL from pool 3 requested work restart
 [2012-12-05 12:54:40] Accepted 5634174c.7bfe87fc GPU 0 pool 3
 [2012-12-05 12:54:42] Accepted 80dff53a.bf5d8415 GPU 0 pool 3
 [2012-12-05 12:54:46] LONGPOLL from pool 3 requested work restart
 [2012-12-05 12:54:51] Accepted b2d828ba.45538286 GPU 1 pool 3
 [2012-12-05 12:54:54] LONGPOLL from pool 3 requested work restart
 [2012-12-05 12:54:57] Accepted efb1033b.86eb6754 GPU 0 pool 3
 [2012-12-05 12:54:59] Accepted ec5af0bc.ca0a720d GPU 1 pool 3
 [2012-12-05 12:55:05] LONGPOLL from pool 3 requested work restart
 [2012-12-05 12:55:05] Accepted bb40cf3f.b7e293bc GPU 2 pool 3

Normal for so many LP restarts? I'm probably getting quite high latencies due to my location. Maybe it's not worth me using p2pool with high latency? Just wondering.

I noticed you have multiple pools setup. Are you using the failoveronly option for cgminer? Unless something has changed and I did not notice you cannot have cgminer process work from other pools at the same time as it processes work for P2pool (something about LP's coming too quickly).

[1714059728]

1714059728

[1714059728]

1714059728

[1714059728]

1714059728

[BkkCoins]

I noticed you have multiple pools setup. Are you using the failoveronly option for cgminer? Unless something has changed and I did not notice you cannot have cgminer process work from other pools at the same time as it processes work for P2pool (something about LP's coming too quickly).

Yes, have Failover-only set True in conf.

This is my pool info display.

Code:

 Queued work requests: 15
 Share submissions: 261
 Accepted shares: 247
 Rejected shares: 14
 Accepted difficulty shares: 247
 Rejected difficulty shares: 14
 Reject ratio: 5.4%

Seems like ok values considering I've heard rejects are usually higher on p2pool. It's still lower than the network reported value around 23%. I guess I'll let it run and figure out if it's working properly.

[aTg]

Pool rate: 330GH/s (21% stale) Share difficulty: 577
Node uptime: 0.376 days Peers: 6 out, 1 in
Local rate: 39.1GH/s (62% DOA) Expected time to share: 0.0177 hours
Shares: 501 total (76 orphaned, 157 dead) Efficiency: 67.76%

I'm on version 9.3, which is going on?

Pool rate: 327GH/s (15% stale) Share difficulty: 634
Node uptime: 0.201 days Peers: 7 out, 2 in
Local rate: 637MH/s (6.7% DOA) Expected time to share: 1.19 hours
Shares: 4 total (0 orphaned, 0 dead) Efficiency: 117.8%

EDIT:When i put less MH/s, rejected rates are more reasonable.

[rav3n_pl]

What is UR mining rig? Also check GBT latency.

[aTg]

What is UR mining rig? Also check GBT latency.

I use FPGA/USB, the hardware is perfectly supported by p2pool in small quantities. What is GBT latency?

[BkkCoins]

I noticed you have multiple pools setup. Are you using the failoveronly option for cgminer? Unless something has changed and I did not notice you cannot have cgminer process work from other pools at the same time as it processes work for P2pool (something about LP's coming too quickly).

Yes, have Failover-only set True in conf.

This is my pool info display.

Code:

 Queued work requests: 15
 Share submissions: 261
 Accepted shares: 247
 Rejected shares: 14
 Accepted difficulty shares: 247
 Rejected difficulty shares: 14
 Reject ratio: 5.4%

Seems like ok values considering I've heard rejects are usually higher on p2pool. It's still lower than the network reported value around 23%. I guess I'll let it run and figure out if it's working properly.

I'm afraid I've given up on p2pool now. After a day of mining I had 5 shares of which 4 were either orphans or rejects. So that's about 75% loss? I simply can't afford to do mining like that with the current difficulty and electric costs. It was a nice idea but I'm going back to my regular pool where I actually get paid to mine. Maybe it's latency issues here but my info above seemed ok.

[forrestv]

P2Pool release 9.4 tag: 9.4 hash: c95830cd6486b848c9201668720072485b2a8aed

Windows binary: http://u.forre.st/u/ahajjytb/p2pool_win32_9.4.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/9.4
Source tarball: https://github.com/forrestv/p2pool/tarball/9.4

Changes:
* Fixed inefficient memory usage - Resident memory went from 736MB to 266MB for Diablo-D3

[rav3n_pl]

P2Pool release 9.4 tag: 9.4 hash: c95830cd6486b848c9201668720072485b2a8aed

Windows binary: http://u.forre.st/u/ahajjytb/p2pool_win32_9.4.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/9.4
Source tarball: https://github.com/forrestv/p2pool/tarball/9.4

Changes:
* Fixed inefficient memory usage - Resident memory went from 736MB to 266MB for Diablo-D3

Yea, it is really nice 263MB res just after start on my 64bit VM Great job forrsetv!

[rav3n_pl]

What is UR mining rig? Also check GBT latency.

I use FPGA/USB, the hardware is perfectly supported by p2pool in small quantities. What is GBT latency?

Bitcoind GetBlockTemplate Latency
See your /static/graphs.html?Hour page and look on graph
Mine is around 0.2s

[aTg]

As I can reduce latency? in another Internet connection, I have 0.5s, ADSL is the problem?

[rav3n_pl]

As I can reduce latency? in another Internet connection, I have 0.5s, ADSL is the problem?

On avg 10s longpool if GBT is ~3s you have fair chance to get work that is already stale :/
IMO it is your bitcoind lagging, try latest git https://github.com/bitcoin/bitcoin
Check your bitcoind and p2pool server CPU usage, maybe it is chocking...

[aTg]

In the two PCs I have version 0.7.1 of bitcoind, one is build 0.7.1-precise1 this is what gives 4s latency over right now and the other is the build 0.7.1-oneiric1 works well but not I think the problem comes from the collection, I end the ideas ...

[cabin]

In the two PCs I have version 0.7.1 of bitcoind, one is build 0.7.1-precise1 this is what gives 4s latency over right now and the other is the build 0.7.1-oneiric1 works well but not I think the problem comes from the collection, I end the ideas ...

Try editing your bitcoin conf with the below settings. The reasoning behind them is with less connections and less transactions to process your bitcoind will respond faster. It did help a lot for me. Also I've noticed that anyone compiling their own bitcoin from git has a big advantage too since the new db system for the next bitcoin release is way faster. If you can't compile your own keep an eye out for a 0.8RC1 when it comes out.

Code:

maxconnections=10

#Maximum size, in bytes, of blocks you create:
blockmaxsize=50000

#How many bytes of the block should be dedicated to high-priority transactions,                                                                                                 
#included regardless of the fees they pay                                                                                                                                 
blockprioritysize=2000

#Minimum block size you want to create; block will be filled with free transactions                                                                                       
#until there are no more or the block reaches this size:                                                                                                                  
blockminsize=0

#Fee-per-kilobyte amount (in BTC) considered the same as "free"                                                                                                                    
#Be careful setting this: if you set it to zero then                                                                                                                      
#a transaction spammer can cheaply fill blocks using                                                                                                                      
#1-satoshi-fee transactions. It should be set above the real                                                                                                              
#cost to you of processing a transaction.                                                                                                                                 
mintxfee=0.0005

[powersync]

P2Pool release 9.4 tag: 9.4 hash: c95830cd6486b848c9201668720072485b2a8aed

Windows binary: http://u.forre.st/u/ahajjytb/p2pool_win32_9.4.zip
Source zipball: https://github.com/forrestv/p2pool/zipball/9.4
Source tarball: https://github.com/forrestv/p2pool/tarball/9.4

Changes:
* Fixed inefficient memory usage - Resident memory went from 736MB to 266MB for Diablo-D3

How are you guys upgrading to not restart to 0?  The last time I upgraded from 9.0 to 9.2 my shares reset to 0 and I lost a day of mining.

PS

[twmz]

How are you guys upgrading to not restart to 0?  The last time I upgraded from 9.0 to 9.2 my shares reset to 0 and I lost a day of mining.

Restarting doesn't reset your earnings or any shares you have previously found.  It just resets the stats that are displayed in the console.

[rav3n_pl]

How are you guys upgrading to not restart to 0?  The last time I upgraded from 9.0 to 9.2 my shares reset to 0 and I lost a day of mining.

Restarting doesn't reset your earnings or any shares you have previously found.  It just resets the stats that are displayed in the console.

It can, if he mine on another address after upgrade aka different/deleted cashed payout address file or another wallet.

[twmz]

How are you guys upgrading to not restart to 0?  The last time I upgraded from 9.0 to 9.2 my shares reset to 0 and I lost a day of mining.

Restarting doesn't reset your earnings or any shares you have previously found.  It just resets the stats that are displayed in the console.

It can, if he mine on another address after upgrade aka different/deleted cashed payout address file or another wallet.

Even if he starts a new address, the old address will still get paid as blocks are found.  Nothing is lost from restarting.

[rav3n_pl]

How are you guys upgrading to not restart to 0?  The last time I upgraded from 9.0 to 9.2 my shares reset to 0 and I lost a day of mining.

Restarting doesn't reset your earnings or any shares you have previously found.  It just resets the stats that are displayed in the console.

It can, if he mine on another address after upgrade aka different/deleted cashed payout address file or another wallet.

Even if he starts a new address, the old address will still get paid as blocks are found.  Nothing is lost from restarting.

Right, he just maybe hit 2day long block

[Aseras]

I use a new address every month, just a habit, plus makes it easy to track income.

[derjanb]

IMO it is your bitcoind lagging, try latest git https://github.com/bitcoin/bitcoin

Thanks a lot!

http://s11.postimage.org/w3jkje473/BGT.jpg

A slight difference.