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

[rav3n_pl]

i got 5 in, but i dont know how to see if people are mining to my public node or not, but it looks nice, got alot of BTC in 6 hours today

Say hello to another 2-day long round.... *facepalm*

[sharky112065]

i got 5 in, but i dont know how to see if people are mining to my public node or not, but it looks nice, got alot of BTC in 6 hours today

Say hello to another 2-day long round.... *facepalm*

Hmm. aadje93 did not mention the L word, but could be just as bad 

[lenny_]

Hi,
I am using p2pool under Linux. Can you please tell me, how to read number of connected incoming and outgoing peers connected to my p2pool node? I can see it in graph and table (in browser), but I woudlike to extract it to Linux terminal, to futher processing.
Thanks in advance.

[cabin]

Data like this might help?

http://p2pool.hopto.org:9332/peer_addresses
or
http://p2pool.hopto.org:9332/local_stats

Hi,
I am using p2pool under Linux. Can you please tell me, how to read number of connected incoming and outgoing peers connected to my p2pool node? I can see it in graph and table (in browser), but I woudlike to extract it to Linux terminal, to futher processing.
Thanks in advance.

[lenny_]

Data like this might help?

http://p2pool.hopto.org:9332/peer_addresses
or
http://p2pool.hopto.org:9332/local_stats

Hi,
I am using p2pool under Linux. Can you please tell me, how to read number of connected incoming and outgoing peers connected to my p2pool node? I can see it in graph and table (in browser), but I woudlike to extract it to Linux terminal, to futher processing.
Thanks in advance.

/local_stats have it Thank you!

[cabin]

Yes, Forrest or anyone else is free to add it or use it. You can just save the html page as it is, all the code is self contained in it. It goes in your web-static dir.

Strange that it is still going on.. my own node and others in this list are finding valid shares still and the efficiency ratings all seem good.

http://p2pool.hopto.org:9332/static/nodes.html

Are you running a standard bitcoind and not an alpha or something?

Yup, I woke up this morning to about 10 orphans - very strange. I restarted everything and have not had any since.....

Edit: I spoke too soon, just got another one......

Would you consider allowing Forrestv to add the nodes link to p2pool/master? If so please contact him on IRC.

It's nice and would be great if it was included in the master branch.

[sharky112065]

Yes, Forrest or anyone else is free to add it or use it. You can just save the html page as it is, all the code is self contained in it. It goes in your web-static dir.

Strange that it is still going on.. my own node and others in this list are finding valid shares still and the efficiency ratings all seem good.

http://p2pool.hopto.org:9332/static/nodes.html

Are you running a standard bitcoind and not an alpha or something?

Yup, I woke up this morning to about 10 orphans - very strange. I restarted everything and have not had any since.....

Edit: I spoke too soon, just got another one......

Would you consider allowing Forrestv to add the nodes link to p2pool/master? If so please contact him on IRC.

It's nice and would be great if it was included in the master branch.

Yep that is what forrestv told me to do as well, but he wanted me to ask you for your permission to include it in master on git. thanks

[BitCoiner2012]

Member of p2pool since August. Just wanted to say I STILL love it! Far superior long live P2Pool!

[bitpop]

Member of p2pool since August. Just wanted to say I STILL love it! Far superior long live P2Pool!

[mdude77]

Code:

Shares: 254 total (20 orphaned, 10 dead) Efficiency: 103.6%

What's wrong this picture?  I'm at 11.8% stale, and I'm > 100% efficient.

I've done everything I can do to get the stale rate down, and I hover between 10% and 12%.

I've:

- changed AV to not scan bitcoin folder or p2pool folder
- changed cgminer to run on 1 thread, and 0 queue
- run p2pool on same box as bitcoin
- run p2pool on different box as bitcoin
- grab the newest version of p2pool every week or so.

I was around 5% before v8 came out. 

What's going on here?  Is this considered normal now?

M

[lenny_]

Code:

Shares: 254 total (20 orphaned, 10 dead) Efficiency: 103.6%

What's wrong this picture?  I'm at 11.8% stale, and I'm > 100% efficient.

I've done everything I can do to get the stale rate down, and I hover between 10% and 12%.

I've:

- changed AV to not scan bitcoin folder or p2pool folder
- changed cgminer to run on 1 thread, and 0 queue
- run p2pool on same box as bitcoin
- run p2pool on different box as bitcoin
- grab the newest version of p2pool every week or so.

I was around 5% before v8 came out. 

What's going on here?  Is this considered normal now?

M

Can you please give your p2pool node address so we can check your stats.

[Syke]

Code:

Shares: 254 total (20 orphaned, 10 dead) Efficiency: 103.6%

What's wrong this picture?  I'm at 11.8% stale, and I'm > 100% efficient.

I've done everything I can do to get the stale rate down, and I hover between 10% and 12%.

What's going on here?  Is this considered normal now?

Code:

Shares: 1895 (123 orphan, 55 dead) Stale rate: ~9.4% (8-11%) Efficiency: ~99.2% (97-101%) 

Yours looks about the same as mine.

[rav3n_pl]

v9 is on master tree git Time to upgrade!

[mdude77]

Code:

Shares: 254 total (20 orphaned, 10 dead) Efficiency: 103.6%

What's wrong this picture?  I'm at 11.8% stale, and I'm > 100% efficient.

I've done everything I can do to get the stale rate down, and I hover between 10% and 12%.

I've:

- changed AV to not scan bitcoin folder or p2pool folder
- changed cgminer to run on 1 thread, and 0 queue
- run p2pool on same box as bitcoin
- run p2pool on different box as bitcoin
- grab the newest version of p2pool every week or so.

I was around 5% before v8 came out. 

What's going on here?  Is this considered normal now?

M

Can you please give your p2pool node address so we can check your stats.

Not public/open.

M

[zvs]

Code:

Shares: 254 total (20 orphaned, 10 dead) Efficiency: 103.6%

What's wrong this picture?  I'm at 11.8% stale, and I'm > 100% efficient.

I've done everything I can do to get the stale rate down, and I hover between 10% and 12%.

I've:

- changed AV to not scan bitcoin folder or p2pool folder
- changed cgminer to run on 1 thread, and 0 queue
- run p2pool on same box as bitcoin
- run p2pool on different box as bitcoin
- grab the newest version of p2pool every week or so.

I was around 5% before v8 came out.  

What's going on here?  Is this considered normal now?

M

were you running close to that 4% dead before?  my # of dead is usually around 0-1%, but last time I tried p2pool, I was getting about 15% orphans.  which has always been the main problem (for me).  doesn't make a lot of sense, since my bitcoind is on a ram drive and has close to 1000 connections.  probably need to use whatever the equivalent of addnode is in bitcoind to my p2pool command line to connect to the top 10 nodes or so (in ghash/s)

(uh, strayed off topic a bit i guess.  your dead % looks high to me, maybe some local network issue w/ higher latency or something?)

ed:

correct me if i'm wrong, but it would work like this?  person x gets a share based on work x, so now people are to have moved on to work y.  1 second later you submit your share based on work x, thus it is recognized as 'dead' by your p2pool client.  for orphans, you would submit your work x and then begin working on work y (as well as anyone else that received your share).  another person submits their work x a second later (not having received yours yet) and sends it to whoever they can on their peer list, and they all begin working on work z.  the people that are working on work z find another share first, so then your submitted share is orphaned

so, then, dead shares would more likely be caused by local network issues or maybe CPU load or something like that, while orphans would more likely be caused by latency outside your local network??

ed2:

err, change the first part to say that you submit your share based on work x, but your p2pool client already recognizes that there's a prior valid solution

[rav3n_pl]

See your /pings page, how many peers are under 100ms?
Mine are:

Code:

61,87
65,97
70,12
80,00
80,52
85,40
95,61
118,94
145,07
150,26
160,93
163,43
172,75
173,06
190,12
204,10
206,24
214,19
234,54
477,99
581,87
867,02

[rdponticelli]

my bitcoind is on a ram drive and has close to 1000 connections.

This doesn't sound good.  You shouldn't have that many connections opened. AFAIK, the network code of the client isn't good, and having so many connections opened may slow down your connection...

[rav3n_pl]

my bitcoind is on a ram drive and has close to 1000 connections.

This doesn't sound good.  You shouldn't have that many connections opened. AFAIK, the network code of the client isn't good, and having so many connections opened may slow down your connection...

Thats too. Se your /static/graphs.html?Hour page and check getwork latency.

[cabin]

You might want to try these settings in bitcoin.conf to improve your bitcoind performance if it is indeed the bottleneck. I've found processing hundreds of transactions can also slow things down so some of these settings limit the number of transactions to a couple hundred.

Code:

#Max number of nodes to connect to. Another possible bottleneck.
maxconnections=20

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

#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

[mdude77]

You might want to try these settings in bitcoin.conf to improve your bitcoind performance if it is indeed the bottleneck. I've found processing hundreds of transactions can also slow things down so some of these settings limit the number of transactions to a couple hundred.

Thanks everyone for your suggestions.

I upgraded p2pool to v9 this morning.  Now, 12 hours later, I'm still looking pretty:

Code:

Shares: 36 total (2 orphaned, 0 dead) Efficiency: 105.7%

That's 5.6% stale.  I'm hoping it stays.

M